All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Pankaj Raghav <pankaj.raghav@linux.dev>
Cc: Christoph Hellwig <hch@lst.de>,
	Zhang Yi <yi.zhang@huaweicloud.com>,
	Pankaj Raghav <p.raghav@samsung.com>,
	zlang@kernel.org, linux-xfs@vger.kernel.org,
	fstests@vger.kernel.org, djwong@kernel.org, yi.zhang@huawei.com,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v2] generic/795: add unaligned boundary test cases for WRITE_ZEROES
Date: Mon, 13 Jul 2026 15:34:49 +0200	[thread overview]
Message-ID: <20260713133449.GA26357@lst.de> (raw)
In-Reply-To: <db3ed600-8a4a-4932-9e4e-2f5a5d27cdd9@linux.dev>

On Mon, Jul 13, 2026 at 03:21:36PM +0200, Pankaj Raghav wrote:
> What about adding an option to io/filemap.c to take a flag that allows calling
> fiemap without FIEMAP_FLAG_SYNC? So this test could depend on xfs_io fiemap command
> with the flag support enabled? I can revert this test to the previous version which uses
> xfs io fiemap instead of filefrag.

That could work, and adding this flag would be useful in general.

It still has the issue that we require bleeding edge tools, but at least
feature detection for the flag would be easy.


      reply	other threads:[~2026-07-13 13:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  8:30 [PATCH v2] generic/795: add unaligned boundary test cases for WRITE_ZEROES Pankaj Raghav
2026-07-10  8:23 ` Zhang Yi
2026-07-13  7:28   ` Pankaj Raghav
2026-07-13 10:04   ` Christoph Hellwig
2026-07-13 13:21     ` Pankaj Raghav
2026-07-13 13:34       ` Christoph Hellwig [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=20260713133449.GA26357@lst.de \
    --to=hch@lst.de \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=pankaj.raghav@linux.dev \
    --cc=yi.zhang@huawei.com \
    --cc=yi.zhang@huaweicloud.com \
    --cc=zlang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.