From: Mike Galbraith <efault@gmx.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
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 16:56:29 +0200 [thread overview]
Message-ID: <1344956189.5477.1.camel@marge.simpson.net> (raw)
In-Reply-To: <1344955168.14924.85.camel@marge.simpson.net>
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.
-Mike
next prev parent reply other threads:[~2012-08-14 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 13:06 [rfc patch] fs,reiserfs: unlock superblock before callling reiserfs_quota_on_mount() Mike Galbraith
2012-08-14 14:23 ` Steven Rostedt
2012-08-14 14:39 ` Mike Galbraith
2012-08-14 14:56 ` Mike Galbraith [this message]
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
2012-08-14 15:15 ` Frederic Weisbecker
2012-08-16 12:44 ` [patch] " Mike Galbraith
2012-08-16 13:05 ` Frederic Weisbecker
2012-08-16 13:49 ` Mike Galbraith
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=1344956189.5477.1.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.