Bug 157725
| Summary: | sysctl -A returns an error | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Ian Laurie <nixuser> |
| Component: | procps | Assignee: | Karel Zak <kzak> |
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | davej, davem, jos, kzak, tao |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHBA-2006-0036 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-03-07 16:46:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 158175, 168429 | ||
|
Description
Ian Laurie
2005-05-14 03:39:21 UTC
$ rpm -qf /sbin/sysctl procps-3.2.5-4 See Bug 144459 รข sysctl reports error: unknown error <...> reading key '<key>' It's fixed in FC4. The full fix require small change in kernel too. I'm not sure if we want to do it in the old kernels too. It might be a regression problem with modes in /proc. Dave, what's your opinion (<=RHEL4)? sounds feasable to me. davem ? I think backporting the fix into <=RHEL4 is fine. DaveJ, it's just the patch you posted to netdev and me a while ago that fixes the ipv4/ipv6 flush file permissions right? If so, just apply it :-) yep. Karel, feel free to reassign this as a kernel bug to me once you've done the necessary changes to procps in U2. thanks. It's bug in both -- kernel and procps. The procps part: bug #158175. *** Bug 162881 has been marked as a duplicate of this bug. *** Oops.. duplicate bug #162881 is more connected with userspace part of the problem, it means bug #158175. It seems there is more files with the same problem: 2.6.9-11.34.EL: $ ls -la /proc/sys/dev/parport/parport0/autoprobe* -r--r--r-- 1 root root 0 Aug 2 04:29 /proc/sys/dev/parport/parport0/autoprobe -r--r--r-- 1 root root 0 Aug 2 04:29 /proc/sys/dev/parport/parport0/autoprobe0 -r--r--r-- 1 root root 0 Aug 2 04:29 /proc/sys/dev/parport/parport0/autoprobe1 -r--r--r-- 1 root root 0 Aug 2 04:29 /proc/sys/dev/parport/parport0/autoprobe2 -r--r--r-- 1 root root 0 Aug 2 04:29 /proc/sys/dev/parport/parport0/autoprobe3 2.6.12-1.1385_FC4: # ls -la /proc/sys/dev/parport/parport0/autoprobe* --w------- 1 root root 0 Aug 2 10:22 /proc/sys/dev/parport/parport0/autoprobe --w------- 1 root root 0 Aug 2 10:22 /proc/sys/dev/parport/parport0/autoprobe0 --w------- 1 root root 0 Aug 2 10:22 /proc/sys/dev/parport/parport0/autoprobe1 --w------- 1 root root 0 Aug 2 10:22 /proc/sys/dev/parport/parport0/autoprobe2 --w------- 1 root root 0 Aug 2 10:22 /proc/sys/dev/parport/parport0/autoprobe3 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-514.html This issue still happens on kernel-2.6.9-22.EL: # uname -r 2.6.9-22.ELsmp # sysctl -a > /dev/null error: unknown error 25 reading key 'dev.parport.parport0.autoprobe3' error: unknown error 25 reading key 'dev.parport.parport0.autoprobe2' error: unknown error 25 reading key 'dev.parport.parport0.autoprobe1' error: unknown error 25 reading key 'dev.parport.parport0.autoprobe0' error: unknown error 25 reading key 'dev.parport.parport0.autoprobe' error: unknown error 25 reading key 'dev.parport.parport0.devices.lp.timeslice' # cd /proc/sys/dev/parport/parport0/ # ls -l autoprobe* -r--r--r-- 1 root root 0 Oct 20 10:30 autoprobe -r--r--r-- 1 root root 0 Oct 20 10:30 autoprobe0 -r--r--r-- 1 root root 0 Oct 20 10:30 autoprobe1 -r--r--r-- 1 root root 0 Oct 20 10:30 autoprobe2 -r--r--r-- 1 root root 0 Oct 20 10:30 autoprobe3 # cd devices/lp # ls -l timeslice -rw-r--r-- 1 root root 0 Oct 20 10:32 timeslice Should those entries also be set to --w------- ? Yes, there have to be --w-------. See my comment #16. that file shouldn't be --w------- at all. It's read only. however, it only outputs data if theres actually a printer connected. (Thats my understanding from reading the code at least). I don't see anything obviously wrong in the kernel side. Can you check that procps handles the case where we return success, but no data correctly ? What's really bizarre is that on my rawhide box, this problem still exists, but I can make it expose itself in different ways depending on where I pipe the output.. (14:39:21:root@nwo:~)# sysctl -a > /dev/null error: "Inappropriate ioctl for device" reading key "dev.parport.parport0.autoprobe3" error: "Inappropriate ioctl for device" reading key "dev.parport.parport0.autoprobe2" error: "Inappropriate ioctl for device" reading key "dev.parport.parport0.autoprobe1" error: "Inappropriate ioctl for device" reading key "dev.parport.parport0.autoprobe0" error: "Inappropriate ioctl for device" reading key "dev.parport.parport0.autoprobe" error: "Inappropriate ioctl for device" reading key "dev.parport.parport0.devices.lp.timeslice" (14:42:37:root@nwo:~)# sysctl -a | head -n1 error: "Success" reading key "dev.parport.parport0.autoprobe3" error: "Success" reading key "dev.parport.parport0.autoprobe2" error: "Success" reading key "dev.parport.parport0.autoprobe1" error: "Success" reading key "dev.parport.parport0.autoprobe0" error: "Success" reading key "dev.parport.parport0.autoprobe" error: "Success" reading key "dev.parport.parport0.devices.lp.timeslice" Sorry, it's user space problem now. The sysctl code expects that fgets()==NULL is error, but it could be empty file too. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0036.html |