From: "yukuai (C)" <yukuai3@huawei.com>
To: <tj@kernel.org>, <axboe@kernel.dk>
Cc: <cgroups@vger.kernel.org>, <linux-block@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <yi.zhang@huawei.com>
Subject: Re: [PATCH] blk-cgroup: fix missing put device in error path from blkg_conf_pref()
Date: Fri, 19 Nov 2021 16:09:30 +0800 [thread overview]
Message-ID: <26541322-e064-d39f-ed39-b463a3cea092@huawei.com> (raw)
In-Reply-To: <20211102020705.2321858-1-yukuai3@huawei.com>
On 2021/11/02 10:07, Yu Kuai wrote:
Hi, Jens
friendly ping ...
Thanks,
Kuai
> If blk_queue_enter() failed due to queue is dying, the
> blkdev_put_no_open() is needed because blkcg_conf_open_bdev() succeeded.
>
> Fixes: 0c9d338c8443 ("blk-cgroup: synchronize blkg creation against policy deactivation")
> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
> ---
> block/blk-cgroup.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
> index 88b1fce90520..663aabfeba18 100644
> --- a/block/blk-cgroup.c
> +++ b/block/blk-cgroup.c
> @@ -640,7 +640,7 @@ int blkg_conf_prep(struct blkcg *blkcg, const struct blkcg_policy *pol,
> */
> ret = blk_queue_enter(q, 0);
> if (ret)
> - return ret;
> + goto fail;
>
> rcu_read_lock();
> spin_lock_irq(&q->queue_lock);
> @@ -676,13 +676,13 @@ int blkg_conf_prep(struct blkcg *blkcg, const struct blkcg_policy *pol,
> new_blkg = blkg_alloc(pos, q, GFP_KERNEL);
> if (unlikely(!new_blkg)) {
> ret = -ENOMEM;
> - goto fail;
> + goto fail_exit_queue;
> }
>
> if (radix_tree_preload(GFP_KERNEL)) {
> blkg_free(new_blkg);
> ret = -ENOMEM;
> - goto fail;
> + goto fail_exit_queue;
> }
>
> rcu_read_lock();
> @@ -722,9 +722,10 @@ int blkg_conf_prep(struct blkcg *blkcg, const struct blkcg_policy *pol,
> fail_unlock:
> spin_unlock_irq(&q->queue_lock);
> rcu_read_unlock();
> +fail_exit_queue:
> + blk_queue_exit(q);
> fail:
> blkdev_put_no_open(bdev);
> - blk_queue_exit(q);
> /*
> * If queue was bypassing, we should retry. Do so after a
> * short msleep(). It isn't strictly necessary but queue
>
next prev parent reply other threads:[~2021-11-19 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 2:07 Yu Kuai
2021-11-06 9:12 ` yukuai (C)
2021-11-15 21:37 ` Tejun Heo
2021-11-19 8:09 ` yukuai (C) [this message]
2021-11-19 13:27 ` 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=26541322-e064-d39f-ed39-b463a3cea092@huawei.com \
--to=yukuai3@huawei.com \
--cc=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yi.zhang@huawei.com \
/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
all inboxes | Powered by JetHome®