From: Patrick McHardy <kaber@trash.net>
To: Athanasius <link@miggy.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 8961] New: BUG triggered by oidentd in netlink code
Date: Sat, 01 Sep 2007 18:38:23 +0200 [thread overview]
Message-ID: <46D9957F.4020101@trash.net> (raw)
In-Reply-To: <20070831123825.GW22067@miggy.org>
Athanasius wrote:
> I'll compile up a new kernel, likely 2.6.22.6, plus this patch, and
> reboot to it tonight. I still don't know *exactly* how to trigger the
> bug on demand though, it's not reocurred since I posted the bug report
> (but had happened about a week before as well).
Thanks. I'm not sure either, it would require two concurrent requests
to be processed, but AFAICS oidentd only uses a single netlink socket.
Perhaps multiple running instances or something else using the inet_diag
interface?
You might be able to trigger it without this patch by running
"while true; do ss -tn; done" while doing ident queries, but
just running the while loop a couple of times in parallel
doesn't seem to trigger it here.
next prev parent reply other threads:[~2007-09-01 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8961-10286@http.bugzilla.kernel.org/>
2007-08-31 1:08 ` [Bugme-new] [Bug 8961] New: BUG triggered by oidentd in netlink code Andrew Morton
2007-08-31 11:05 ` Patrick McHardy
2007-08-31 12:38 ` Athanasius
2007-09-01 16:38 ` Patrick McHardy [this message]
2007-09-01 17:39 ` Athanasius
2007-09-01 22:53 ` Patrick McHardy
2007-09-02 4:04 ` Herbert Xu
2007-09-02 10:56 ` Patrick McHardy
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=46D9957F.4020101@trash.net \
--to=kaber@trash.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=link@miggy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).