From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: dipankar@in.ibm.com
Cc: syrius.ml@no-log.org, Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
bero@arklinux.org, sharyath@in.ibm.com
Subject: Re: 2.6.12-mm1: BUG() in fd_install, RCU related?
Date: Thu, 23 Jun 2005 23:47:03 +0200 [thread overview]
Message-ID: <200506232347.04396.rjw@sisk.pl> (raw)
In-Reply-To: <20050623190218.GA4999@in.ibm.com>
Hi,
On Thursday, 23 of June 2005 21:02, Dipankar Sarma wrote:
> On Thu, Jun 23, 2005 at 01:50:11PM +0200, syrius.ml@no-log.org wrote:
> > Dipankar Sarma <dipankar@in.ibm.com> writes:
> >
> > > Some things are common - always with fcntl() or fcntl64() and with
> > > a daemon. Does your box come up at all ? If so, can you get me an
> > > strace on the process that triggers this ? If I can narrow it
> > > down to a small testcase, it would be a lot easier. Also, does
> > > switching off CONFIG_PREEMPT fix this problem ?
> >
> > I haven't read about this thread. I hope u'll find a way to reproduce
> > it. here debian/sid i386 (.config sent in an earlier message), it 100%
> > reproducible when restarting bind9. (it also happens on its own on
> > different occasion)
> >
> >
> > then i restart the daemon:
> >
> > end of a strace -f /etc/init.d/bind9 start
> > 6541 rt_sigaction(SIGPIPE, {0xb7ca2a70, [], 0}, {SIG_IGN}, 8) = 0
> > 6541 send(3, "<30>Jun 23 00:51:35 named[6540]:"..., 82, 0) = 82
> > 6541 rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
> > 6541 socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 10
> > 6541 fcntl64(10, F_DUPFD, 20) = 32
> > 6541 close(10) = 0
> > 6541 fcntl64(32, F_GETFL) = 0x2 (flags O_RDWR)
> > 6541 fcntl64(32, F_SETFL, O_RDWR|O_NONBLOCK) = 0
> > 6541 setsockopt(32, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
> > 6541 setsockopt(32, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
> > 6541 bind(32, {sa_family=AF_INET, sin_port=htons(53),
> > sin_addr=inet_addr("172.16.254.1")}, 16) = 0
> > 6541 socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 10
> > 6541 fcntl64(10, F_DUPFD, 20
>
> Aha, this has been extremely helpful. Could you all please try the
> following (untested) patch ? This should fix the problem, or
> atleast one problem that I can see.
On my system the patch apparently fixes the problem. Excellent job! :-)
Thanks,
Rafael
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2005-06-23 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-21 8:34 2.6.12-mm1: BUG() in fd_install, RCU related? Pavel Machek
2005-06-21 9:07 ` Dipankar Sarma
2005-06-21 9:15 ` Pavel Machek
2005-06-23 11:50 ` syrius.ml
2005-06-23 19:02 ` Dipankar Sarma
2005-06-23 21:47 ` Rafael J. Wysocki [this message]
2005-06-23 23:05 ` syrius.ml
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=200506232347.04396.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=bero@arklinux.org \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sharyath@in.ibm.com \
--cc=syrius.ml@no-log.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