From: NeilBrown <neilb@suse.de>
To: Theodore Tso <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org,
"Paul E.McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: RCU locking issues in jbd2_dev_to_name
Date: Thu, 28 Jul 2011 08:45:31 +1000 [thread overview]
Message-ID: <20110728084531.06aa878a@notabene.brown> (raw)
In-Reply-To: <7A69E96B-0763-4440-BE10-A39B808C44FA@mit.edu>
On Wed, 27 Jul 2011 07:28:27 -0400 Theodore Tso <tytso@MIT.EDU> wrote:
>
> On Jul 27, 2011, at 3:41 AM, NeilBrown wrote:
>
> >
> >
> > Hi Ted and all,
> >
> > I've been exploring RCU usage in the kernel looking for strange things, and
> > jbd2_dev_to_name looks particularly strange. The following patch explains
> > and addresses the issues that I found. Comments welcome.
>
> Yeah its broken. But I have patches pending for the merge window that solve
> it by nuking the function altogether; the problem is calling a function from
> TP_PRINTK causes perf to die on the spot, terminating its tracing. :-(
>
Sounds painful...
If it is about to go, that is good enough for me.
Thanks,
NeilBrown
prev parent reply other threads:[~2011-07-27 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110727174104.65fb9c1c@notabene.brown>
2011-07-27 11:28 ` RCU locking issues in jbd2_dev_to_name Theodore Tso
2011-07-27 22:45 ` NeilBrown [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=20110728084531.06aa878a@notabene.brown \
--to=neilb@suse.de \
--cc=linux-ext4@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tytso@MIT.EDU \
/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;
as well as URLs for NNTP newsgroup(s).