From: Patrick McHardy <kaber@trash.net>
To: Athanasius <link@miggy.org>, Patrick McHardy <kaber@trash.net>,
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: Sun, 02 Sep 2007 00:53:29 +0200 [thread overview]
Message-ID: <46D9ED69.7030706@trash.net> (raw)
In-Reply-To: <20070901173944.GB3693@miggy.org>
Athanasius wrote:
> On Sat, Sep 01, 2007 at 06:38:23PM +0200, Patrick McHardy wrote:
>>
>> 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.
>
> I went for setting up a dummy listener in inetd, using tcpd, and
> setting hosts.allow to specify myuser@ip. Then a few while loops
> spamming it with connections using nc.
>
> Anyway, on the old kernel that managed to trigger the BUG twice in
> about 30 minutes. I'm now on 2.6.22.6 plus your patch and coming up on
> an hour (55+ mins) of the same and no sign of the BUG.
>
> So that looks like fixed to me. I'll weigh in again if the daily
> logcheck throws up another.
Thanks a lot for testing, I'll send a version for current -rc
upstream tommorrow.
WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Athanasius <link@miggy.org>, Patrick McHardy <kaber@trash.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
netdev@vger.kernel.org, bugme-d
Subject: Re: [Bugme-new] [Bug 8961] New: BUG triggered by oidentd in netlink code
Date: Sun, 02 Sep 2007 00:53:29 +0200 [thread overview]
Message-ID: <46D9ED69.7030706@trash.net> (raw)
In-Reply-To: <20070901173944.GB3693@miggy.org>
Athanasius wrote:
> On Sat, Sep 01, 2007 at 06:38:23PM +0200, Patrick McHardy wrote:
>>
>> 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.
>
> I went for setting up a dummy listener in inetd, using tcpd, and
> setting hosts.allow to specify myuser@ip. Then a few while loops
> spamming it with connections using nc.
>
> Anyway, on the old kernel that managed to trigger the BUG twice in
> about 30 minutes. I'm now on 2.6.22.6 plus your patch and coming up on
> an hour (55+ mins) of the same and no sign of the BUG.
>
> So that looks like fixed to me. I'll weigh in again if the daily
> logcheck throws up another.
Thanks a lot for testing, I'll send a version for current -rc
upstream tommorrow.
next prev parent reply other threads:[~2007-09-01 22:53 UTC|newest]
Thread overview: 9+ 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
2007-09-01 17:39 ` Athanasius
2007-09-01 22:53 ` Patrick McHardy [this message]
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=46D9ED69.7030706@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.