From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: davem@redhat.com
Cc: Robert Love <rml@tech9.net>,
linux-kernel@vger.kernel.org,
roger.larsson@skelletftea.mail.telia.com
Subject: Re: Preempt count check when leaving IRQ? (Was: Re: 2.5.44
Date: Thu, 7 Nov 2002 23:52:01 +0200 [thread overview]
Message-ID: <6DEAE382FC9@vcnet.vc.cvut.cz> (raw)
On 7 Nov 02 at 1:41, Roger Larsson wrote:
>
> This is another CHECK to do then.
>
> Make a copy of preempt count when entering an IRQ.
> Check that we have the same value when leaving.
> (using -acX we only have to add the check when leaving)
Hi Dave,
I have bad news for you: doing 'cat /proc/net/arp' sometime kills
my system hard.
Problem is with reading /proc/net/arp: arp_seq_start does
read_lock_bh(&arp_tbl.lock), and this lock is held and held and held...
as long as neigh_get_bucket() returns non-NULL, or until reading
of /proc/net/arp stops...
... and so it sometime happens that lock is still held when accessing
userspace while copying data in read, and shortly after that we run
userspace with (1) this lock held and (2) bh disabled, and scheduler
does not like such configuration.
I'd say that all machines here are affected, and only I suffer
from problem because of I'm running shell script which periodically pings
all machines on subnet, reading their ethernet addresses back from
/proc/net/arp...
Unfortunately I do not have any idea how to fix it correctly, so for now
I just removed /proc/net/arp from my system, because of 'cat /proc/net/arp'
preceded by ping is quickest way I know to kill my system from user account.
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
reply other threads:[~2002-11-07 22:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6DEAE382FC9@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=roger.larsson@skelletftea.mail.telia.com \
/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