From: "Barry K. Nathan" <barryn@pobox.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: Valdis.Kletnieks@vt.edu, "Andrew Morton" <akpm@osdl.org>,
arjan@linux.intel.com, linux-kernel@vger.kernel.org,
reiserfs-dev@namesys.com
Subject: Re: 2.6.17-rc5-mm3: bad unlock ordering (reiser4?)
Date: Sun, 4 Jun 2006 15:03:12 -0700 [thread overview]
Message-ID: <986ed62e0606041503v701f8882la4cbead47ae3982f@mail.gmail.com> (raw)
In-Reply-To: <20060604213432.GB5898@elte.hu>
On 6/4/06, Ingo Molnar <mingo@elte.hu> wrote:
> nevertheless i'll turn that warning into a less scary message.
This discussion seems to imply that I reported a false positive... is
it *known* that I reported a false positive, or is it only a strong
possibility?
Assuming it's a false positive: Since this stops the tracer, it means
that if an actual deadlock possibility is detected later [I'm assuming
that detection of those doesn't get shut down by the bad-lock-ordering
detection either], useful information could be missing from
/proc/latency_trace, if I am not mistaken. Perhaps this could impede
lockdep testing for people running reiser4 filesystems. I guess this
is just a theoretical possibility at this point, but perhaps it's
worth mentioning.
--
-Barry K. Nathan <barryn@pobox.com>
next prev parent reply other threads:[~2006-06-04 22:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-04 12:04 Barry K. Nathan
2006-06-04 14:00 ` Barry K. Nathan
2006-06-04 20:33 ` Andrew Morton
2006-06-04 20:56 ` Valdis.Kletnieks
2006-06-04 21:34 ` Ingo Molnar
2006-06-04 22:03 ` Barry K. Nathan [this message]
2006-06-05 2:46 ` Hans Reiser
2006-06-05 6:54 ` Ingo Molnar
2006-06-05 7:37 ` Ingo Molnar
2006-06-05 11:22 ` Alexander Zarochentsev
2006-06-05 12:50 ` Ingo Molnar
2006-06-05 23:56 ` Hans Reiser
2006-06-05 7:58 ` Barry K. Nathan
2006-06-05 8:12 ` Ingo Molnar
2006-06-05 9:00 ` Barry K. Nathan
2006-06-09 21:39 ` Hans Reiser
2006-06-09 21:36 ` Hans Reiser
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=986ed62e0606041503v701f8882la4cbead47ae3982f@mail.gmail.com \
--to=barryn@pobox.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=reiserfs-dev@namesys.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®