From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, bwindle@fint.org, acme@conectiva.com.br
Subject: Re: 2.5.46-bk3: BUG in skbuff.c:178
Date: Fri, 8 Nov 2002 21:33:24 +0200 [thread overview]
Message-ID: <6F45EB551A2@vcnet.vc.cvut.cz> (raw)
On 8 Nov 02 at 12:01, Andrew Morton wrote:
> > Single-CPU system, running 2.5.46-bk3. Whiling compiling bk4, and running
> > a script that was pinging every host on my subnet (I was running arp -a
> > to see what was in the arp table at the time), I hit this BUG.
>
> I'd be suspecting the seq_file conversion in arp.c. The read_lock_bh()
> stuff in there looks, umm, unclear ;)
Yes, see my emails from 23th Oct, 25th Oct (2.5.44: Strange oopses from
userspace), from Nov 6th + Nov 7th: Preempt count check when leaving
IRQ.
But while yesterday I had no idea, today I have one (it looks like that
nobody else is going to fix it for me :-( ) :
seq subsystem can call arp_seq_start/next/stop several times, but
state->is_pneigh is set to 0 only once, by memset in arp_seq_open :-(
I think that arp_seq_start should do
{
+ struct arp_iter_state* state = seq->private;
+ seq->is_pneigh = 0;
+ seq->bucket = 0;
read_lock_bh(&arp_tbl.lock);
return *pos ? arp_get_bucket(seq, pos) : (void *)1;
}
and we can drop memset from arp_seq_open. I'll try it, and if it will
survive my tests, I'll send real patch.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-11-08 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 19:33 Petr Vandrovec [this message]
2002-11-08 22:02 ` 2.5.46-bk3: BUG in skbuff.c:178 Petr Vandrovec
2002-11-10 4:18 ` Arnaldo Carvalho de Melo
2002-11-11 2:26 ` Petr Vandrovec
2002-11-11 2:42 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 19:42 Burton Windle
2002-11-08 20:01 ` Andrew Morton
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=6F45EB551A2@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=acme@conectiva.com.br \
--cc=akpm@digeo.com \
--cc=bwindle@fint.org \
--cc=linux-kernel@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