From: Herbert Poetzl <herbert@13thfloor.at>
To: Dawson Engler <engler@csl.stanford.edu>
Cc: viro@parcelfarce.linux.theplanet.co.uk,
Dawson Engler <engler@coverity.dreamhost.com>,
linux-kernel@vger.kernel.org, developers@coverity.com
Subject: Re: [CHECKER] possible reiserfs deadlock in 2.6.8.1
Date: Sun, 12 Sep 2004 20:37:30 +0200 [thread overview]
Message-ID: <20040912183729.GA22865@MAIL.13thfloor.at> (raw)
In-Reply-To: <200409080510.i885ANcX025884@csl.stanford.edu>
On Tue, Sep 07, 2004 at 10:10:23PM -0700, Dawson Engler wrote:
> > On Tue, Sep 07, 2004 at 08:16:53PM -0700, Dawson Engler wrote:
> > > Hi All,
Hey Dawson!
> > > below is a possible deadlock in the linux-2.6.8.1 reiserfs code found by
> > > a static deadlock checker I'm writing. Let me know if it looks valid
is this tool somewhere available? via CVS or similar?
I would be interested in analyzing some kernel patches
with it. if it isn't available, maybe you could check
some patches with it, and send/publish the results?
TIA,
Herbert
> > > and/or whether the output is too cryptic. Note, one of the locks is
> > > through a struct pointer, so the deadlock depends on both acquisitions
> > > being to the same struct.
> >
> > Not valid, for the same reason as the above. BKL and down() do not form
> > a mutual deadlock.
>
> You know, I actually know this, and the tool "does" take care of this.
> I think a bit mask got screwed up somewhere. Along with my brain...
>
> Sorry about the noise.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2004-09-12 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 3:16 Dawson Engler
2004-09-08 3:36 ` viro
2004-09-08 5:10 ` Dawson Engler
2004-09-12 18:37 ` Herbert Poetzl [this message]
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=20040912183729.GA22865@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=developers@coverity.com \
--cc=engler@coverity.dreamhost.com \
--cc=engler@csl.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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®