From: Mike Galbraith <efault@gmx.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [rfc patch] fs,reiserfs: unlock superblock before callling reiserfs_quota_on_mount()
Date: Tue, 14 Aug 2012 20:09:57 +0200 [thread overview]
Message-ID: <1344967797.4282.8.camel@marge.simpson.net> (raw)
In-Reply-To: <1344966273.6724.18.camel@gandalf.stny.rr.com>
On Tue, 2012-08-14 at 13:44 -0400, Steven Rostedt wrote:
> On Tue, 2012-08-14 at 19:26 +0200, Mike Galbraith wrote:
> > On Tue, 2012-08-14 at 17:18 +0200, Thomas Gleixner wrote:
> > > On Tue, 14 Aug 2012, Mike Galbraith wrote:
> > >
> > > > On Tue, 2012-08-14 at 16:39 +0200, Mike Galbraith wrote:
> > > > > On Tue, 2012-08-14 at 10:23 -0400, Steven Rostedt wrote:
> > > > > > On Tue, 2012-08-14 at 15:06 +0200, Mike Galbraith wrote:
> > > > > > > Greetings,
> > > > > > >
> > > > > > > Using openSUSE's "partitioner" gizmo to set up a reiserfs partition with
> > > > > > > quotas and whatnot enabled rewarded me with a deadlock.
> > > > > >
> > > > > > Is this just a -rt bug? Can't this deadlock also in mainline?
> > > > >
> > > > > It didn't with a NOPREEMPT kernel the one time I tried it, which seemed
> > > > > mighty odd when I stared at the rt deadlock. I'll give it another go, I
> > > > > likely just munged q/d NOPREEMPT test.
> > > >
> > > > Nope, no screw-up. Maybe it can deadlock, but it refused to do so.
> > >
> > > Lockdep should tell you if it could ...
> >
> > I'll give that a shot. I would expect the thing to gripe.. but then I
> > expected the damn thing to deadlock properly with NOPREEMPT too, so.. :)
> >
>
> But would it?
>
> We have kworker blocked on the mutex where the owner did a flush_work(),
> and waiting for kworker to finish because of a wait_for_completion(). I
> don't see annotation here that will help lockdep catch such a thing.
Hm.. <zzzt>. Ok, you saved me a long kernel build, but cost me a fuse.
-Mike
prev parent reply other threads:[~2012-08-14 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1344949583.14924.36.camel@marge.simpson.net>
2012-08-14 14:23 ` [rfc patch] fs,reiserfs: unlock superblock before callling reiserfs_quota_on_mount() Steven Rostedt
2012-08-14 14:39 ` Mike Galbraith
2012-08-14 14:56 ` Mike Galbraith
2012-08-14 15:18 ` Thomas Gleixner
2012-08-14 17:26 ` Mike Galbraith
2012-08-14 17:44 ` Steven Rostedt
2012-08-14 18:09 ` Mike Galbraith [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=1344967797.4282.8.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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