From: Pavel Machek <pavel@denx.de>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
Anand Jain <anand.jain@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Dominique Martinet <dominique.martinet@atmark-techno.com>,
Pavel Machek <pavel@denx.de>,
stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: add missing mutex_unlock in btrfs_relocate_sys_chunks()
Date: Fri, 19 Apr 2024 11:17:16 +0200 [thread overview]
Message-ID: <ZiI2nIYK0X6RLciF@duo.ucw.cz> (raw)
In-Reply-To: <20240419-btrfs_unlock-v1-1-c3557976a691@codewreck.org>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
On Fri 2024-04-19 11:22:48, Dominique Martinet wrote:
> From: Dominique Martinet <dominique.martinet@atmark-techno.com>
>
> The previous patch forgot to unlock in the error path
>
> Link: https://lore.kernel.org/all/Zh%2fHpAGFqa7YAFuM@duo.ucw.cz
> Reported-by: Pavel Machek <pavel@denx.de>
> Cc: stable@vger.kernel.org
> Fixes: 7411055db5ce ("btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks()")
> Signed-off-by: Dominique Martinet<dominique.martinet@atmark-techno.com>
Reviewed-by: Pavel Machek <pavel@denx.de>
Thank you!
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-04-19 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 2:22 [PATCH] btrfs: add missing mutex_unlock in btrfs_relocate_sys_chunks() Dominique Martinet
2024-04-19 9:17 ` Pavel Machek [this message]
2024-04-23 14:38 ` David Sterba
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=ZiI2nIYK0X6RLciF@duo.ucw.cz \
--to=pavel@denx.de \
--cc=anand.jain@oracle.com \
--cc=asmadeus@codewreck.org \
--cc=clm@fb.com \
--cc=dominique.martinet@atmark-techno.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).