The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Jeremy Bingham <jbingham@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	brauner@kernel.org, jkoolstra@xs4all.nl, jack@suse.cz,
	viro@zeniv.linux.org.uk
Subject: Re: [PATCH v3 0/5] minix: convert to iomap and add direct I/O
Date: Mon, 13 Jul 2026 17:53:52 -0700	[thread overview]
Message-ID: <20260714005352.GA7398@frogsfrogsfrogs> (raw)
In-Reply-To: <CAMyBmMDj7e0t8J2rYTw4uBe9SMDx0Jyf1iDbbcKYMdq3zzEEHg@mail.gmail.com>

On Mon, Jul 13, 2026 at 12:26:27PM -0700, Jeremy Bingham wrote:
> On Mon, Jul 13, 2026 at 2:32 AM Christoph Hellwig <hch@infradead.org> wrote:
> >
> > On Sat, Jul 11, 2026 at 01:59:04PM -0700, Jeremy Bingham wrote:
> >
> > There's no point explaining each patch in the over letter, that's
> > what the commit log for each patch are for.
> 
> Understood. I've also read your other reply about how the cover letter
> and commits need to explain *why* rather than *how* and will fix
> them accordingly.
> 
> > How did you test this?  How do the xfstests auto group results look
> > with an without the series for minix?
> 
> I made a script that exercises about 40 different file and directory
> operations against each version of the minix filesystem. I tried running
> xfstests against minix with and without these patches, but it doesn't
> work under either case because mkfs.minix and fsck.minix don't take
> the expected arguments. I had backed off using xfstests for this
> because of that, but I'll revisit with the next round of changes.

Yes, please do get fstests working /before/ you start changing critical
file IO paths.

--D

> Thank you again for your comments,
> 
> -j

      reply	other threads:[~2026-07-14  0:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 20:59 [PATCH v3 0/5] minix: convert to iomap and add direct I/O Jeremy Bingham
2026-07-11 20:59 ` [PATCH v3 1/5] iomap: add iomap_symlink_write Jeremy Bingham
2026-07-13  9:44   ` Christoph Hellwig
2026-07-11 20:59 ` [PATCH v3 2/5] minix: add base iomap begin/end functions Jeremy Bingham
2026-07-13  9:46   ` Christoph Hellwig
2026-07-11 20:59 ` [PATCH v3 3/5] minix: update itree* files to add iomap functions Jeremy Bingham
2026-07-11 20:59 ` [PATCH v3 4/5] minix: add file operation functions Jeremy Bingham
2026-07-13  9:48   ` Christoph Hellwig
2026-07-13 19:17     ` Jeremy Bingham
2026-07-11 20:59 ` [PATCH v3 5/5] minix: iomap inode operations Jeremy Bingham
2026-07-13  9:32 ` [PATCH v3 0/5] minix: convert to iomap and add direct I/O Christoph Hellwig
2026-07-13 19:26   ` Jeremy Bingham
2026-07-14  0:53     ` Darrick J. Wong [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=20260714005352.GA7398@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=brauner@kernel.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jbingham@gmail.com \
    --cc=jkoolstra@xs4all.nl \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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