public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: fdmanana@kernel.org
Cc: linux-btrfs@vger.kernel.org, ian@ianjohnson.dev,
	Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 0/2] btrfs: updates for directory reading
Date: Mon, 11 Sep 2023 13:35:30 -0400	[thread overview]
Message-ID: <20230911173530.GB2352074@perftesting> (raw)
In-Reply-To: <cover.1694260751.git.fdmanana@suse.com>

On Sat, Sep 09, 2023 at 01:08:30PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> 
> Tweak and fix a bug when reading directory entries after a rewinddir(3)
> call. Reported by Ian Johnson.
> 
> Link: https://lore.kernel.org/linux-btrfs/YR1P0S.NGASEG570GJ8@ianjohnson.dev/T/#u
> 
> Filipe Manana (2):
>   btrfs: set last dir index to the current last index when opening dir
>   btrfs: refresh dir last index during a rewinddir(3) call
> 
>  fs/btrfs/inode.c | 18 ++++++++++++++++--
>  1 file changed, 16 insertions(+), 2 deletions(-)
> 

Reviewed-by: Josef Bacik <josef@toxicpanda.com>

I didn't see an fstest for this, is it forthcoming?  Thanks,

Josef

  parent reply	other threads:[~2023-09-11 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 12:08 [PATCH 0/2] btrfs: updates for directory reading fdmanana
2023-09-09 12:08 ` [PATCH 1/2] btrfs: set last dir index to the current last index when opening dir fdmanana
2023-09-11 10:40   ` Filipe Manana
2023-09-09 12:08 ` [PATCH 2/2] btrfs: refresh dir last index during a rewinddir(3) call fdmanana
2023-09-11 10:36   ` Filipe Manana
2023-09-11 17:28 ` [PATCH 0/2] btrfs: updates for directory reading David Sterba
2023-09-11 17:35 ` Josef Bacik [this message]
2023-09-11 17:40   ` Filipe Manana

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=20230911173530.GB2352074@perftesting \
    --to=josef@toxicpanda.com \
    --cc=fdmanana@kernel.org \
    --cc=fdmanana@suse.com \
    --cc=ian@ianjohnson.dev \
    --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