From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Tino Keitel <tino.keitel@gmx.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
James Bottomley <James.Bottomley@SteelEye.com>,
Boaz Harrosh <bharrosh@panasas.com>, Alan Cox <alan@redhat.com>
Subject: Re: 2.6.24-rc6-git7: Reported regressions from 2.6.23
Date: Tue, 1 Jan 2008 21:38:14 -0800 [thread overview]
Message-ID: <20080102053814.GB25586@kroah.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0801011408470.32517@woody.linux-foundation.org>
On Tue, Jan 01, 2008 at 02:26:06PM -0800, Linus Torvalds wrote:
>
>
> On Tue, 1 Jan 2008, Rafael J. Wysocki wrote:
> >
> > Subject : Could not set non-blocking flag with 2.6.24-rc5
> > Submitter : Tino Keitel <tino.keitel@gmx.de>
> > Date : 2007-12-13 16:27
> > References : http://lkml.org/lkml/2007/12/13/392
> > http://bugzilla.kernel.org/show_bug.cgi?id=9557
> > Handled-By :
> > Patch :
>
> That strace shows that trying to open /dev/null fails with ENXIO:
>
> [pid 6050] open("/dev/null", O_RDONLY <unfinished ...>
> [pid 6050] <... open resumed> ) = -1 ENXIO (No such device or address)
>
> and everything goes downhill from there.
>
> It would be worth looking at your /dev/null to see what kind of (broken)
> device node it is, and get a clue about *why* it is broken.
>
> Greg, any udev breakage that could affect /dev/null?
I do not know of any such breakage.
But, as this is in a chroot, hopefully udev has properly populated the
chrooted /dev tree for the process to provide the /dev/null device node?
Tino, did you provide a /dev/ for your chroot? Did you use udev to
create it, or did you use a static /dev tree?
thanks,
greg k-h
next prev parent reply other threads:[~2008-01-02 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 21:02 2.6.24-rc6-git7: Reported regressions from 2.6.23 Rafael J. Wysocki
2008-01-01 22:26 ` Linus Torvalds
2008-01-02 3:30 ` James Bottomley
2008-01-02 11:00 ` Ingo Molnar
2008-01-02 5:38 ` Greg KH [this message]
2008-01-02 3:12 ` Zhenyu Wang
2008-01-02 13:12 ` Rafael J. Wysocki
2008-01-02 13:24 ` Ingo Molnar
2008-01-02 13:37 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080102053814.GB25586@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tino.keitel@gmx.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox