Kernel Bug Tracker – Bug 9557
Could not set non-blocking flag with 2.6.24-rc5
Last modified: 2008-01-13 13:22:47 UTC
Subject : Could not set non-blocking flag with 2.6.24-rc5
Submitter : Tino Keitel <email@example.com>
References : http://lkml.org/lkml/2007/12/13/392
> [pid 5988] fcntl64(-1, F_GETFL) = -1 EBADF (Bad file descriptor)
Err... '-1' has always been an illegal value for a file descriptor. POSIX
tells you explicitly that if open() or creat() return -1, then that is a
sign of an error. I'm surprised that aptitude isn't checking for that.
That said, could you show the part from the strace that actually contains the
open() that failed?
Created attachment 14098 [details]
working run with 184.108.40.206 in a chroot
Created attachment 14099 [details]
broken run with 2.6.24-rc5 in a chroot
Created attachment 14100 [details]
working run with 220.127.116.11 outside a chroot
Created attachment 14101 [details]
working run with 2.6.24-rc5 outside a chroot
I attached some complete strace outputs of the working and the broken condision. I hope that helps.
At least for the chroot case, you're getting
open("/dev/null", O_RDWR) = -1 ENXIO (No such device or address)
which to me implies that you have a broken /dev, possibly due to some
odd udev issue or just your chroot environment getting broken by
The chroot is extracted from the same .tar.gz in each of the above cases. I'll check if I can see what's wrong with /dev/null in the error case.
Tino, any updates?
I can not reproduce it anymore with 2.6.24-rc4.
Closing as unreproducible. Please reopen if it reappears.
Err, I meant 2.6.24-rc7 (I was told that this was a XFS issue that is fixed in 2.6.24-rc7).