From: Josef Bacik <josef@toxicpanda.com>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs: fix for btrfs_prev_leaf() and unexport it
Date: Wed, 12 Apr 2023 09:47:08 -0400 [thread overview]
Message-ID: <20230412134708.GA3162142@perftesting> (raw)
In-Reply-To: <cover.1681295111.git.fdmanana@suse.com>
On Wed, Apr 12, 2023 at 11:33:08AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> A fix for btrfs_prev_leaf() where due to races with concurrent insertions,
> can return the same key again, and unexport it since it's not used outside
> ctree.c. More details on the individual changelogs.
>
> Filipe Manana (2):
> btrfs: fix btrfs_prev_leaf() to not return the same key twice
> btrfs: unexport btrfs_prev_leaf()
>
> fs/btrfs/ctree.c | 131 +++++++++++++++++++++++++++++------------------
> fs/btrfs/ctree.h | 1 -
> 2 files changed, 81 insertions(+), 51 deletions(-)
>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2023-04-12 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 10:33 [PATCH 0/2] btrfs: fix for btrfs_prev_leaf() and unexport it fdmanana
2023-04-12 10:33 ` [PATCH 1/2] btrfs: fix btrfs_prev_leaf() to not return the same key twice fdmanana
2023-04-13 19:57 ` Wang Yugui
2023-04-14 3:43 ` Wang Yugui
2023-04-17 10:18 ` Filipe Manana
2023-04-12 10:33 ` [PATCH 2/2] btrfs: unexport btrfs_prev_leaf() fdmanana
2023-04-15 7:14 ` Anand Jain
2023-04-12 13:47 ` Josef Bacik [this message]
2023-04-17 18:53 ` [PATCH 0/2] btrfs: fix for btrfs_prev_leaf() and unexport it 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=20230412134708.GA3162142@perftesting \
--to=josef@toxicpanda.com \
--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