From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Larry Bassel <larry.bassel@oracle.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y] btrfs: don't abort filesystem when attempting to snapshot deleted subvolume
Date: Wed, 25 Jun 2025 10:07:23 -0400 [thread overview]
Message-ID: <20250624213237-d32dd2bd102e09d7@stable.kernel.org> (raw)
In-Reply-To: <20250623220816.51405-1-larry.bassel@oracle.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 7081929ab2572920e94d70be3d332e5c9f97095a
WARNING: Author mismatch between patch and upstream commit:
Backport author: Larry Bassel<larry.bassel@oracle.com>
Commit author: Omar Sandoval<osandov@fb.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: ec794a752819)
6.1.y | Present (different SHA1: 6e6bca99e8d8)
5.15.y | Present (different SHA1: 0877497dc978)
5.10.y | Present (different SHA1: 2bdf872bcfe6)
Note: The patch differs from the upstream commit:
---
1: 7081929ab2572 < -: ------------- btrfs: don't abort filesystem when attempting to snapshot deleted subvolume
-: ------------- > 1: db0e7a8388dcf btrfs: don't abort filesystem when attempting to snapshot deleted subvolume
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y | Success | Success |
prev parent reply other threads:[~2025-06-25 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 22:08 [PATCH 5.4.y] btrfs: don't abort filesystem when attempting to snapshot deleted subvolume Larry Bassel
2025-06-25 14:07 ` Sasha Levin [this message]
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=20250624213237-d32dd2bd102e09d7@stable.kernel.org \
--to=sashal@kernel.org \
--cc=larry.bassel@oracle.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 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).