All of lore.kernel.org
 help / color / mirror / Atom feed
From: mturquette@linaro.org (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: Really fix deadlock with mmap_sem
Date: Fri, 12 Dec 2014 15:24:16 -0800	[thread overview]
Message-ID: <20141212232416.20398.58297@quantum> (raw)
In-Reply-To: <20141212230543.GX11285@n2100.arm.linux.org.uk>

Quoting Russell King - ARM Linux (2014-12-12 15:05:43)
> On Fri, Dec 12, 2014 at 03:04:16PM -0800, Stephen Boyd wrote:
> > Commit 6314b6796e3c (clk: Don't hold prepare_lock across debugfs
> > creation, 2014-09-04) forgot to update one place where we hold
> > the prepare_lock while creating debugfs directories. This means
> > we still have the chance of a deadlock that the commit was trying
> > to fix. Actually fix it by moving the debugfs creation outside
> > the prepare_lock.
> > 
> > Reported-by: Russell King - ARM Linux <linux@arm.linux.org.uk>
> 
> Please use "Russell King <rmk+kernel@arm.linux.org.uk>" rather than this
> address, thanks.

Applied to clk-next and fixed up the email address locally.

Regards,
Mike

> 
> -- 
> FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
> according to speedtest.net.

WARNING: multiple messages have this Message-ID (diff)
From: Mike Turquette <mturquette@linaro.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	"Stephen Boyd" <sboyd@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: Really fix deadlock with mmap_sem
Date: Fri, 12 Dec 2014 15:24:16 -0800	[thread overview]
Message-ID: <20141212232416.20398.58297@quantum> (raw)
In-Reply-To: <20141212230543.GX11285@n2100.arm.linux.org.uk>

Quoting Russell King - ARM Linux (2014-12-12 15:05:43)
> On Fri, Dec 12, 2014 at 03:04:16PM -0800, Stephen Boyd wrote:
> > Commit 6314b6796e3c (clk: Don't hold prepare_lock across debugfs
> > creation, 2014-09-04) forgot to update one place where we hold
> > the prepare_lock while creating debugfs directories. This means
> > we still have the chance of a deadlock that the commit was trying
> > to fix. Actually fix it by moving the debugfs creation outside
> > the prepare_lock.
> > 
> > Reported-by: Russell King - ARM Linux <linux@arm.linux.org.uk>
> 
> Please use "Russell King <rmk+kernel@arm.linux.org.uk>" rather than this
> address, thanks.

Applied to clk-next and fixed up the email address locally.

Regards,
Mike

> 
> -- 
> FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
> according to speedtest.net.

  reply	other threads:[~2014-12-12 23:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 23:04 [PATCH] clk: Really fix deadlock with mmap_sem Stephen Boyd
2014-12-12 23:04 ` Stephen Boyd
2014-12-12 23:05 ` Russell King - ARM Linux
2014-12-12 23:05   ` Russell King - ARM Linux
2014-12-12 23:24   ` Mike Turquette [this message]
2014-12-12 23:24     ` Mike Turquette
2014-12-12 23:26     ` Russell King - ARM Linux
2014-12-12 23:26       ` Russell King - ARM Linux
2014-12-16  1:18       ` Mike Turquette
2014-12-13  0:13 ` Thomas Gleixner
2014-12-13  0:13   ` Thomas Gleixner

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=20141212232416.20398.58297@quantum \
    --to=mturquette@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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.