From: NeilBrown <neilb@suse.de>
To: Jens Axboe <axboe@fb.com>
Cc: Keith Busch <keith.busch@intel.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: LOCKDEP warning due to ext_devt_lock
Date: Thu, 28 May 2015 13:45:11 +1000 [thread overview]
Message-ID: <20150528134511.27f9bdbc@notabene.brown> (raw)
In-Reply-To: <55668C45.3060700@fb.com>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
On Wed, 27 May 2015 21:32:21 -0600 Jens Axboe <axboe@fb.com> wrote:
> On 05/27/2015 08:32 PM, NeilBrown wrote:
> >
> > Hi Keith,
> > I'm getting lockdep warning around use of ext_devt_lock.
> >
> > [11428.266019] inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
> >
> > As you say in
> > 2da78092dda1 ("block: Fix dev_t minor allocation lifetime")
> > ext_devt_lock can be taken from call_rcu's soft-irq.
> > I think that means it should always use the _irq verion of spinlock.
>
> Wouldn't spin_lock_bh() and friends suffice then?
>
Quite possibly. I've never actually used those so I don't tend to think
about them. But only reflection I think they would be exactly right.
I'll modify my patch for future testing.
BTW, did you get my:
[PATCH v2] block: discard bdi_unregister() in favour of bdi_destroy()
?? I haven't seen it appear in your 'block' tree.
Thanks,
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-05-28 3:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 2:32 LOCKDEP warning due to ext_devt_lock NeilBrown
2015-05-28 3:32 ` Jens Axboe
2015-05-28 3:45 ` NeilBrown [this message]
2015-05-28 16:13 ` Jens Axboe
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=20150528134511.27f9bdbc@notabene.brown \
--to=neilb@suse.de \
--cc=axboe@fb.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.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 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).