Bug 1450980

Summary: kacpimon returns warrning about too many connections
Product: Red Hat Enterprise Linux 7 Reporter: Andrej Manduch <amanduch>
Component: acpidAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED ERRATA QA Contact: Andrej Manduch <amanduch>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: emcnabb, thozza
Target Milestone: rcKeywords: FastFix, Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: acpid-2.0.19-9.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 10:09:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Proposed fix sent upstream none

Description Andrej Manduch 2017-05-15 13:36:26 UTC 
Description of problem:

Kacpimon return warnings about too many connection when there are more than 20 devices in /dev/input/


Version-Release number of selected component (if applicable):


How reproducible:
every time

Steps to Reproduce:
1. just run this script:
```
#!/bin/bash

set -x
for i in `seq 1 200`; do
        mknod /dev/input/event${i} c 13 63
done
```
2. run kacpimon


Actual results:

kacpimon will return this warning:

/dev/input/event99 (Unknown) opened successfully
add_connection(): Too many connections.
Netlink ACPI Family ID: 22
Netlink ACPI Multicast Group ID: 2
netlink opened successfully
add_connection(): Too many connections.
Press Escape to exit, or Ctrl-C if that doesn't work.

Expected results:

acpid support up to 1024 connections, kacpimoin should support same number
Comment 5 Jaroslav Škarvada 2017-08-31 10:13:00 UTC 
Created attachment 1320538 [details]
Proposed fix sent upstream

Upstream ticket: https://sourceforge.net/p/acpid2/tickets/14/
Comment 10 errata-xmlrpc 2018-04-10 10:09:22 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0696