All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Pankaj Raghav <pankaj.raghav@linux.dev>, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-xfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, stable@vger.kernel.org,
	da.gomez@kernel.org, gost.dev@samsung.com
Subject: Re: [PATCH] iomap: only follow dio alignment requirement if specified
Date: Tue, 27 Oct 2026 20:42:59 +1030	[thread overview]
Message-ID: <04a7e656-567d-458c-99b0-e9aa5960bd99@gmx.com> (raw)
In-Reply-To: <0046bdae-1dd1-4f4b-a1e5-9eb7fe8b5fe0@linux.dev>



在 2026/10/27 20:37, Pankaj Raghav 写道:
> 
> 
[...]
>>>> Cc: stable@vger.kernel.org
> 
> FYI, your patches are not in 7.3 and only in linux-next. So we don't 
> need to cc stable?

Unfortunately, it's already upstreamed.

The commit hash, 4025185cf953 ("iomap: follow the alignment requirement 
for iomap_dio_hole_iter()"), is already in the upstream.

Thanks,
Qu

>>>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>>>> ---
>>>>   fs/iomap/direct-io.c | 26 ++++++++++++++++----------
>>>>   1 file changed, 16 insertions(+), 10 deletions(-)
>>>>
>>>
>>> Ignore my previous question (I had a old version of xfstests).
>>> I was able to reproduce the error on XFS, ext4 and this patch fixes it.
>>>
>>> One small nit: should we update the IOMAP_DIO_FSBLOCK_ALIGNED flag
>>> documentation to reflect this?
>>>
>>> At the moment the document says "Ensure each bio is aligned to fs block
>>> size". Should we expand it to say "Ensure each bio and any progress
>>> reported for hole/unwritten extents is aligned to fs block size"?
>>
>> I'll change it to something like "Ensure every operation, including 
>> bio and folio zeroing, is aligned to fs block size".
>>
> 
> This is better.
>> Will be included in the next update.
>>
> 
> And for the b4 error, feel free to use:
> Reviewed-by: Pankaj Raghav(Samsung) <pankaj.raghav@linux.dev>
> 
> -- 
> Pankaj


  reply	other threads:[~2026-10-27 10:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  6:48 [PATCH] iomap: only follow dio alignment requirement if specified Qu Wenruo
2026-10-26 14:21 ` Pankaj Raghav (Samsung)
2026-10-26 19:49 ` Pankaj Raghav (Samsung)
2026-10-26 20:59   ` Qu Wenruo
2026-10-26 21:29     ` Qu Wenruo
2026-10-27 10:07     ` Pankaj Raghav
2026-10-27 10:12       ` Qu Wenruo [this message]
2026-10-27 11:14         ` Pankaj Raghav

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=04a7e656-567d-458c-99b0-e9aa5960bd99@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=da.gomez@kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=pankaj.raghav@linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=wqu@suse.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 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.