From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "longman@redhat.com" <longman@redhat.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Cc: "bfields@fieldses.org" <bfields@fieldses.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"jlayton@poochiereds.net" <jlayton@poochiereds.net>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2] blktrace: Fix potentail deadlock between delete & sysfs ops
Date: Thu, 17 Aug 2017 20:41:10 +0000 [thread overview]
Message-ID: <1503002469.2615.13.camel@wdc.com> (raw)
In-Reply-To: <20170817163056.19ea42c8@gandalf.local.home>
On Thu, 2017-08-17 at 16:30 -0400, Steven Rostedt wrote:
> On Thu, 17 Aug 2017 12:24:39 -0400
> Waiman Long <longman@redhat.com> wrote:
>
> > On 08/17/2017 09:34 AM, Steven Rostedt wrote:
> > > On Wed, 16 Aug 2017 16:40:40 -0400
> > > Waiman Long <longman@redhat.com> wrote:
> > >
> > > > The lockdep code had reported the following unsafe locking scenario:
> > > >
> > > > CPU0 CPU1
> > > > ---- ----
> > > > lock(s_active#228);
> > > > lock(&bdev->bd_mutex/1);
> > > > lock(s_active#228);
> > > > lock(&bdev->bd_mutex);
> > >
> > > Can you show the exact locations of these locks. I have no idea where
> > > this "s_active" is.
> >
> > The s_active isn't an actual lock. It is a reference count (kn->count)
> > on the sysfs (kernfs) file. Removal of a sysfs file, however, require
> > a wait until all the references are gone. The reference count is
> > treated like a rwsem using lockdep instrumentation code.
>
> Which kernel is this? I don't see any lockdep annotation around
> kn->count (doing a git grep, I find it referenced in fs/kernfs/dir.c)
As far as I know the s_active lockdep annotations were introduced in 2007
through commit 0ab66088c855 ("sysfs: implement sysfs_dirent active reference
and immediate disconnect"). Today these annotations exist in kernfs:
$ git grep -nHw dep_map fs/kernfs
fs/kernfs/dir.c:421: rwsem_acquire_read(&kn->dep_map, 0, 1, _RET_IP_);
fs/kernfs/dir.c:441: rwsem_release(&kn->dep_map, 1, _RET_IP_);
fs/kernfs/dir.c:468: rwsem_acquire(&kn->dep_map, 0, 0, _RET_IP_);
fs/kernfs/dir.c:470: lock_contended(&kn->dep_map, _RET_IP_);
fs/kernfs/dir.c:478: lock_acquired(&kn->dep_map, _RET_IP_);
fs/kernfs/dir.c:479: rwsem_release(&kn->dep_map, 1, _RET_IP_);
fs/kernfs/dir.c:1385: rwsem_acquire(&kn->dep_map, 0, 1, _RET_IP_);
fs/kernfs/file.c:1000: lockdep_init_map(&kn->dep_map, "s_active", key, 0);
Bart.
next prev parent reply other threads:[~2017-08-17 20:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 20:40 [PATCH v2] blktrace: Fix potentail deadlock between delete & sysfs ops Waiman Long
2017-08-17 13:34 ` Steven Rostedt
2017-08-17 16:24 ` Waiman Long
2017-08-17 20:30 ` Steven Rostedt
2017-08-17 20:41 ` Bart Van Assche [this message]
2017-08-17 20:56 ` Steven Rostedt
2017-08-17 21:10 ` Steven Rostedt
2017-08-17 21:27 ` Waiman Long
2017-08-17 22:13 ` Steven Rostedt
2017-08-17 22:18 ` Steven Rostedt
2017-08-17 23:23 ` Steven Rostedt
2017-08-18 13:42 ` Waiman Long
2017-08-17 21:30 ` Steven Rostedt
2017-08-18 13:55 ` Waiman Long
2017-08-18 16:21 ` Bart Van Assche
2017-08-18 17:22 ` Waiman Long
2017-08-18 17:26 ` Steven Rostedt
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=1503002469.2615.13.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.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).