From: David Sterba <dsterba@suse.cz>
To: Omar Sandoval <osandov@osandov.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 0/2] btrfs: subvolume deletion vs. snapshot fixes
Date: Mon, 8 Jan 2024 20:39:35 +0100 [thread overview]
Message-ID: <20240108193935.GH28693@twin.jikos.cz> (raw)
In-Reply-To: <cover.1704397423.git.osandov@fb.com>
On Thu, Jan 04, 2024 at 11:48:45AM -0800, Omar Sandoval wrote:
> 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
Added to misc-next, thanks.
prev parent reply other threads:[~2024-01-08 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 19:48 [PATCH v2 0/2] btrfs: subvolume deletion vs. snapshot fixes Omar Sandoval
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 [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=20240108193935.GH28693@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@osandov.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