From: Vivek Goyal <vgoyal@redhat.com>
To: Joe Lawrence <joe.lawrence@stratus.com>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: docker crashes rcuos in __blkg_release_rcu
Date: Tue, 10 Jun 2014 15:14:53 -0400 [thread overview]
Message-ID: <20140610191453.GD17337@redhat.com> (raw)
In-Reply-To: <20140610143906.0d2f35d0@jlaw-desktop.mno.stratus.com>
On Tue, Jun 10, 2014 at 02:39:06PM -0400, Joe Lawrence wrote:
[..]
> > I am wondering if we need to take a reference on the queue
> > (blk_get_queue()) in blkg_alloc(), to make sure request queue is
> > still around when blkg is being freed.
>
> I experimented with this and the crash does go away (and the docker
> invocation completes successfully). I wasn't sure where the
> accompanying blk_put_queue() should go. If I put it in blkg_free, the
> kref accounting doesn't seem to even out, ie they never fall to zero.
I think blkg_free() is logical place to put down queue reference. I am
not sure why it does not even out. Will spend some time on this.
>
> > I will try to reproduce the issue locally.
>
> Any luck? I found that slub_debug was required to draw out the crash,
> otherwise the use-after-free silently goes about its business.
I had tried it yesterday and saw the crash out of 3 attempts. I am
right now busy in something. Give me 1-2 days and I will be able to
spend more time on this problem.
Thanks
Vivek
next prev parent reply other threads:[~2014-06-10 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 22:22 Joe Lawrence
2014-06-09 17:47 ` Vivek Goyal
2014-06-09 18:27 ` Vivek Goyal
2014-06-10 18:39 ` Joe Lawrence
2014-06-10 19:14 ` Vivek Goyal [this message]
2014-06-11 16:32 ` Vivek Goyal
2014-06-19 20:26 ` Tejun Heo
2014-06-19 21:42 ` [PATCH block/for-linus] blkcg: fix use-after-free in __blkg_release_rcu() by making blkcg_gq refcnt an atomic_t Tejun Heo
2014-06-20 14:39 ` Vivek Goyal
2014-06-20 18:50 ` Jens Axboe
2014-06-20 18:50 ` Joe Lawrence
2014-06-10 19:52 ` docker crashes rcuos in __blkg_release_rcu Christoph Lameter
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=20140610191453.GD17337@redhat.com \
--to=vgoyal@redhat.com \
--cc=joe.lawrence@stratus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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
Powered by JetHome