Linux filesystem development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Sun Yongjian <sunyongjian1@huawei.com>,
	linux-fsdevel@vger.kernel.org, yangerkun@huawei.com
Subject: Re: [PATCH] Revert "libfs: Use d_children list to iterate simple_offset directories"
Date: Wed, 12 Mar 2025 08:39:49 -0700	[thread overview]
Message-ID: <Z9GqxXvyXB_aR_Wu@infradead.org> (raw)
In-Reply-To: <vg5mnmd5qar5cck2qezeimkhjrs6cqgwb2xd6togm6sp6ac7or@dahqij46fml6>

On Tue, Mar 11, 2025 at 05:47:18PM -0400, Kent Overstreet wrote:
> > guarantee that d_off will always increase in value as an application
> > walks the directory. That's an impossible thing to guarantee given
> > the way d_off values are chosen (at entry creation time, not at
> > directory iteration time).
> 
> Not sure why you're trying to cite POSIX when it's an actual application
> regression under discussion.

Because from what Darrick report they look very related.

> Sane d_offset behaviour is one of those "of _course_ things will break
> you screw that up and I don't want to be on the hook for debugging it"
> things to filesystem developers - you don't do it.

Yet the semantics are surprisingly underdocument, where the issues show
up is rather surprising and non-obvious and people do tend to get it
wrong surprisingly often (probably this thread, a whole bunch of btrfs
things showing up, the old v1 xfs format, etc).

I've actually started collection various issues in the past, the test
cases that triggered it and how it relates to writtent standards.  It's
a bit of a mess.  I hope to eventually have a coherent writeup on all
that.


  reply	other threads:[~2025-03-12 15:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26 14:29 [PATCH] Revert "libfs: Use d_children list to iterate simple_offset directories" Greg Kroah-Hartman
2025-02-26 15:57 ` Chuck Lever
2025-02-26 16:21   ` Greg Kroah-Hartman
2025-02-26 16:28     ` Chuck Lever
2025-02-26 19:13       ` Greg Kroah-Hartman
2025-02-26 20:33         ` Chuck Lever
2025-03-10 16:29           ` Greg Kroah-Hartman
2025-03-10 17:30             ` Chuck Lever
2025-03-11 13:55               ` Sun Yongjian
2025-03-11 15:23                 ` Chuck Lever
2025-03-11 18:11                   ` Darrick J. Wong
2025-03-11 18:25                     ` Chuck Lever
2025-03-11 18:52                       ` Darrick J. Wong
2025-03-11 19:39                         ` Chuck Lever
2025-03-11 21:47                           ` Kent Overstreet
2025-03-12 15:39                             ` Christoph Hellwig [this message]
2025-03-12 15:47                           ` Christoph Hellwig
2025-03-13 13:45                   ` Chuck Lever
2025-03-18 11:38                     ` Sun Yongjian

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=Z9GqxXvyXB_aR_Wu@infradead.org \
    --to=hch@infradead.org \
    --cc=chuck.lever@oracle.com \
    --cc=djwong@kernel.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sunyongjian1@huawei.com \
    --cc=yangerkun@huawei.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