From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Tino Keitel <tino.keitel@gmx.de>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Could not set non-blocking flag with 2.6.24-rc5
Date: Fri, 14 Dec 2007 01:45:39 +0100 [thread overview]
Message-ID: <200712140145.39791.rjw@sisk.pl> (raw)
In-Reply-To: <20071213201601.GA5831@dose.home.local>
On Thursday, 13 of December 2007, Tino Keitel wrote:
> Hi folks,
>
> I often build Debian packages inside a chroot. Today I discovered a
> failure during an "aptitude update", which is a command to download new
> package lists for the package management. In strace, the lines around
> the failure look like this:
>
> 99% [Working]) = 14 14
> [pid 5986] select(6, [3 4 5], [], NULL, {0, 500000}) = 0 (Timeout)
> [pid 5986] gettimeofday({1197576353, 670510}, NULL) = 0
> [pid 5986] rt_sigprocmask(SIG_BLOCK, [WINCH], [], 8) = 0
> [pid 5986] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> 99% [Working]) = 14 14
> [pid 5986] select(6, [3 4 5], [], NULL, {0, 500000}) = 0 (Timeout)
> [pid 5986] gettimeofday({1197576354, 173902}, NULL) = 0
> [pid 5986] rt_sigprocmask(SIG_BLOCK, [WINCH], [], 8) = 0
> [pid 5986] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> 99% [Working]) = 14 14
> [pid 5986] select(6, [3 4 5], [], NULL, {0, 500000} <unfinished ...>
> [pid 5988] <... select resumed> ) = 1 (in [3], left {105, 0})
> [pid 5988] read(3, "", 56559) = 0
> [pid 5988] fcntl64(-1, F_GETFL) = -1 EBADF (Bad file
> descriptor)
> [pid 5988] fcntl64(-1, F_SETFL,
> O_ACCMODE|O_CREAT|O_EXCL|O_NOCTTY|O_TRUNC|O_APPEND|O_SYNC|O_ASYNC|O_DIRECT|O_LARGEFILE|O_DIRECTORY|O_NOFOLLOW|O_NOATIME|0xfff8003c)
> = -1 EBADF (Bad file descriptor)
> [pid 5988] write(2, ""..., 41FATAL -> Could not set non-blocking flag
> ) = 41
> [pid 5988] write(2, ""..., 19Bad file descriptor) = 19
> [pid 5988] write(2, ""..., 1
> ) = 1
> [pid 5988] exit_group(100) = ?
> Process 5988 detached
>
> This happened with a kernel after 2.6.24-rc5
> (4af75653031c6d454b4ace47c1536f0d2e727e3e). I rebooted into 2.6.23.8
> and it worked. Now I rebooted into 2.6.24-rc5 again and was able to
> reproduce the failure, so it looks like a kernel issue to me.
Yes, it does.
I'm not sure who to forward it to, though. Andrew, can you help, please?
next prev parent reply other threads:[~2007-12-14 0:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 20:16 Could not set non-blocking flag with 2.6.24-rc5 Tino Keitel
2007-12-14 0:45 ` Rafael J. Wysocki [this message]
2007-12-17 10:27 ` Andrew Morton
2007-12-18 0:28 ` Rafael J. Wysocki
2008-01-12 21:10 ` Christoph Hellwig
2008-01-13 8:56 ` Tino Keitel
2008-01-13 18:22 ` Tino Keitel
[not found] <fa.2D6HRLjr6ibJZfUZ3+G8Q2ex4ig@ifi.uio.no>
2007-12-15 2:52 ` Robert Hancock
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=200712140145.39791.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tino.keitel@gmx.de \
/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