From: Ian Johnson <ian@ianjohnson.dev>
To: Filipe Manana <fdmanana@kernel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Possible readdir regression with BTRFS
Date: Sat, 09 Sep 2023 15:27:37 -0400 [thread overview]
Message-ID: <1QGQ0S.784N7IZ653TH3@ianjohnson.dev> (raw)
In-Reply-To: <ZPxiDy1vZE5VIF93@debian0.Home>
On Sat, Sep 9 2023 at 01:16:15 PM +01:00:00, Filipe Manana
<fdmanana@kernel.org> wrote:
> Here it is (I CC'ed you, but just to link the thread):
>
> https://lore.kernel.org/linux-btrfs/cover.1694260751.git.fdmanana@suse.com/
Thank you! I've applied the patchset at my end and confirmed that it
works both for my sample program (prints neither 1 nor 2 if rewinddir is
not used, and prints both if it is) and for the other project I was
originally debugging.
prev parent reply other threads:[~2023-09-09 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 1:07 Possible readdir regression with BTRFS Ian Johnson
2023-09-09 7:27 ` Filipe Manana
2023-09-09 11:52 ` Evangelos Foutras
2023-09-09 12:18 ` Filipe Manana
2023-09-11 11:56 ` Filipe Manana
2023-09-09 12:16 ` Filipe Manana
2023-09-09 19:27 ` Ian Johnson [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=1QGQ0S.784N7IZ653TH3@ianjohnson.dev \
--to=ian@ianjohnson.dev \
--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;
as well as URLs for NNTP newsgroup(s).