From: Omar Sandoval <osandov@osandov.com>
To: linux-btrfs@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [PATCH v2 0/2] btrfs: subvolume deletion vs. snapshot fixes
Date: Thu, 4 Jan 2024 11:48:45 -0800 [thread overview]
Message-ID: <cover.1704397423.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Hi,
This small series fixes a couple of bugs that can happen when trying to
snapshot a deleted subvolume. Patch 1 fixes a filesystem abort that we
hit in production. Patch 2 fixes another issue that Sweet Tea spotted
when reviewing patch 1.
An fstest was sent previously [1].
Thanks!
Changes from v1 [2]:
- Rebased on latest misc-next.
- Added patch 2.
1: https://lore.kernel.org/linux-btrfs/62415ffc97ff2db4fa65cdd6f9db6ddead8105cd.1703010806.git.osandov@osandov.com/
2: https://lore.kernel.org/linux-btrfs/068014bd3e90668525c295660862db2932e25087.1703010314.git.osandov@fb.com/
Omar Sandoval (2):
btrfs: don't abort filesystem when attempting to snapshot deleted
subvolume
btrfs: avoid copying BTRFS_ROOT_SUBVOL_DEAD flag to snapshot of
subvolume being deleted
fs/btrfs/inode.c | 22 +++++++++++++---------
fs/btrfs/ioctl.c | 3 +++
2 files changed, 16 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2024-01-04 19:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 19:48 Omar Sandoval [this message]
2024-01-04 19:48 ` [PATCH v2 1/2] btrfs: don't abort filesystem when attempting to snapshot deleted subvolume Omar Sandoval
2024-01-04 19:48 ` [PATCH v2 2/2] btrfs: avoid copying BTRFS_ROOT_SUBVOL_DEAD flag to snapshot of subvolume being deleted Omar Sandoval
2024-01-05 20:11 ` [PATCH v2 0/2] btrfs: subvolume deletion vs. snapshot fixes Sweet Tea Dorminy
2024-01-06 0:58 ` Anand Jain
2024-01-08 19:39 ` 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=cover.1704397423.git.osandov@fb.com \
--to=osandov@osandov.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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