From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: linux-kernel@vger.kernel.org
Cc: Stephan von Krawczynski <skraw@ithnet.com>
Subject: Re: Race condition in 2.4 tasklet handling (cli() broken?)
Date: Mon, 25 Aug 2003 10:06:33 +0200 [thread overview]
Message-ID: <200308250806.h7P86X413480@oboe.it.uc3m.es> (raw)
In-Reply-To: <nKwX.1yy.17@gated-at.bofh.it>
In article <nKwX.1yy.17@gated-at.bofh.it> you wrote:
> On Sun, 24 Aug 2003 00:13:15 +0900
> TeJun Huh <tejun@aratech.co.kr> wrote:
>> The race conditions I'm mentioning in this thread are not likely to
>> cause real troubles. The first one does not make any difference on
>> x86, and AFAIK bh isn't used extensively anymore so the second one
>> isn't very relevant either. Only the race condition mentioned in the
>> other thread is of relvance if there is any :-(.
> Are you sure? bh is used in fs subtree to my knowledge ...
Would someone care to spemd a moment to tell me what the spin_lock_bh
does that spin_lock alone does not do? (not just "local_bh_disable",
pleasse :-). I am chasing SMP oopses for filesystems mounted on nbd
which only seem to happen in association with high memory stress (and
possibly "high memory"), and I suspect I am going to be interested by
the answer.
There is no commentary that I can find in the source, beyond the
assembler code in local_bh_enable().
Peter
next parent reply other threads:[~2003-08-25 8:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <nKwX.1yy.17@gated-at.bofh.it>
2003-08-25 8:06 ` Peter T. Breuer [this message]
2003-08-23 2:54 Race condition in 2.4 tasklet handling TeJun Huh
2003-08-23 4:09 ` Race condition in 2.4 tasklet handling (cli() broken?) TeJun Huh
2003-08-23 5:26 ` TeJun Huh
2003-08-23 10:28 ` Stephan von Krawczynski
2003-08-23 15:13 ` TeJun Huh
2003-08-23 15:37 ` Stephan von Krawczynski
2003-08-25 6:31 ` TeJun Huh
2003-08-25 7:23 ` Stephan von Krawczynski
2003-08-26 0:27 ` TeJun Huh
2003-08-23 15:56 ` Stephan von Krawczynski
2003-08-23 16:36 ` TeJun Huh
2003-08-24 3:27 ` TeJun Huh
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=200308250806.h7P86X413480@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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
all inboxes | Powered by JetHome®