mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH][v3.2 stable tree] dcache: Balance rcu_read_lock in have_submounts()
Date: Mon, 16 Feb 2015 00:03:17 +0000	[thread overview]
Message-ID: <1424044997.23608.21.camel@decadent.org.uk> (raw)
In-Reply-To: <20150212002850.146cf455@grimm.local.home>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

On Thu, 2015-02-12 at 00:28 -0500, Steven Rostedt wrote:
> On Wed, 11 Feb 2015 03:15:37 +0000
> Ben Hutchings <ben@decadent.org.uk> wrote:
> 
> > I've reviewed locking contexts in all three functions that I changed
> > when backporting "deal with deadlock in d_walk()".  It's actually worse
> > than you say:
> > 
> > - We don't hold this_parent->d_lock at the 'positive' label in
> > have_submounts(), but it is unlocked after 'rename_retry'.
> > - There is an rcu_read_unlock() after the 'out' label in
> > select_parent(), but it's not held at the 'goto out'.
> > 
> > Does the following patch work for you?
> 
> I booted the original 3.2 kernel 3 times and it succeeded once, and
> crashed the other two.
> 
> I applied this patch and booted it 5 times, and it succeeded every time.
> 
> I removed the patch, and it crashed on the very next boot.
> 
> Thus, I'd say it seems to have fixed the issue for me.
> 
> Tested-by: Steven Rostedt <rostedt@goodmis.org>
[...]

Thanks.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

      reply	other threads:[~2015-02-16  0:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17 15:38 Steven Rostedt
2015-02-11  3:15 ` Ben Hutchings
2015-02-12  5:28   ` Steven Rostedt
2015-02-16  0:03     ` Ben Hutchings [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=1424044997.23608.21.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.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®