From: David Sterba <dsterba@suse.cz>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: fix missing delayed items run after unlink during log replay
Date: Tue, 1 Mar 2022 16:35:23 +0100 [thread overview]
Message-ID: <20220301153523.GO12643@twin.jikos.cz> (raw)
In-Reply-To: <cover.1646064823.git.fdmanana@suse.com>
On Mon, Feb 28, 2022 at 04:29:27PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> This fixes a couple places that miss running delayed items after doing an
> unlink during log replay. The first patch is the actual fix, while the
> second one is just a small refactoring to avoid duplication.
>
> Filipe Manana (2):
> btrfs: add missing run of delayed items after unlink during log replay
> btrfs: add and use helper for unlinking inode during log replay
Added to misc-next, thanks.
prev parent reply other threads:[~2022-03-01 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 16:29 [PATCH 0/2] btrfs: fix missing delayed items run after unlink during log replay fdmanana
2022-02-28 16:29 ` [PATCH 1/2] btrfs: add missing run of delayed items " fdmanana
2022-02-28 16:29 ` [PATCH 2/2] btrfs: add and use helper for unlinking inode " fdmanana
2022-03-01 15:35 ` 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=20220301153523.GO12643@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--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