From: Greg KH <gregkh@linuxfoundation.org>
To: yangerkun <yangerkun@huawei.com>
Cc: Sasha Levin <sashal@kernel.org>,
linux-stable <stable@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [BUG REPORT] Incorrect adaptation of 7e49538288e5 ("loop: Avoid updating block size under exclusive owner") for stable 6.6
Date: Mon, 29 Sep 2025 15:28:22 +0200 [thread overview]
Message-ID: <2025092911-grappling-tutor-8f40@gregkh> (raw)
In-Reply-To: <7f6f5d7d-385d-ea47-43b8-bbd6341e2ec6@huawei.com>
On Wed, Sep 24, 2025 at 10:36:19AM +0800, yangerkun wrote:
> Error path for blk_validate_block_size is wrong, we should goto unlock, or
> lo_mutex won't be release, and bdev will keep claimed.
Can you provide a working patch we can apply?
thanks,
greg k-h
next prev parent reply other threads:[~2025-09-29 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 2:36 [BUG REPORT] Incorrect adaptation of 7e49538288e5 ("loop: Avoid updating block size under exclusive owner") for stable 6.6 yangerkun
2025-09-29 13:28 ` Greg KH [this message]
2025-09-30 3:42 ` yangerkun
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=2025092911-grappling-tutor-8f40@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yangerkun@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