From: Chao Yu <chao@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: chao@kernel.org, Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH] src/min_dio_alignment: don't return invalid dio_offset_align
Date: Wed, 11 Sep 2024 18:10:59 +0800 [thread overview]
Message-ID: <648a1578-eccc-4c9d-8d27-2c87dbb71e06@kernel.org> (raw)
In-Reply-To: <20240911074641.GA5629@lst.de>
On 2024/9/11 15:46, Christoph Hellwig wrote:
> although one day we might want to do something smarted with this
> information. That being said a file system not supporting direct
> I/O is a bit silly these days. What is running into this?
After applying commit 5c8764f8679e ("f2fs: fix to force buffered IO
on inline_data inode"), inline_data enabled tmpfile shows it doesn't
support DIO, then it results in deadloop of generic/465.
prev parent reply other threads:[~2024-09-11 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 3:53 [PATCH] src/min_dio_alignment: don't return invalid dio_offset_align Chao Yu
2024-09-11 7:46 ` Christoph Hellwig
2024-09-11 10:10 ` Chao Yu [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=648a1578-eccc-4c9d-8d27-2c87dbb71e06@kernel.org \
--to=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=zlang@redhat.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