From: Sasha Levin <sashal@kernel.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] blk-mq: not embed .mq_kobj and ctx->kobj into queue instance
Date: Fri, 16 Nov 2018 01:52:05 -0500 [thread overview]
Message-ID: <20181116065205.GD1706@sasha-vm> (raw)
In-Reply-To: <20181116032826.11901-2-ming.lei@redhat.com>
On Fri, Nov 16, 2018 at 11:28:25AM +0800, Ming Lei wrote:
>Even though .mq_kobj, ctx->kobj and q->kobj share same lifetime
>from block layer's view, actually they don't because userspace may
>grab one kobject anytime via sysfs, so each kobject's lifetime has
>to be independent, then the objects(mq_kobj, ctx) which hosts its
>own kobject have to be allocated dynamically.
>
>This patch fixes kernel panic issue during booting when DEBUG_KOBJECT_RELEASE
>is enabled.
>
>Reported-by: Guenter Roeck <linux@roeck-us.net>
>Cc: Guenter Roeck <linux@roeck-us.net>
>Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>Cc: stable@vger.kernel.org
>Signed-off-by: Ming Lei <ming.lei@redhat.com>
What does this patch depend on? It doesn't apply to Linus's tree nor to
the block tree.
Also, could you please cc lkml with patches?
--
Thanks,
Sasha
next prev parent reply other threads:[~2018-11-16 6:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 3:28 [PATCH 0/2] blk-mq: fix kobject lifetime issue Ming Lei
2018-11-16 3:28 ` [PATCH 1/2] blk-mq: not embed .mq_kobj and ctx->kobj into queue instance Ming Lei
2018-11-16 6:11 ` jianchao.wang
2018-11-16 7:52 ` Ming Lei
2018-11-16 6:52 ` Sasha Levin [this message]
2018-11-16 7:49 ` Ming Lei
2018-11-16 16:07 ` Sasha Levin
2018-11-16 3:28 ` [PATCH 2/2] blk-mq: alloc q->queue_ctx as normal array Ming Lei
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=20181116065205.GD1706@sasha-vm \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-block@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ming.lei@redhat.com \
--cc=stable@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 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.