Thread (26 messages) 26 messages, 5 authors, 2023-09-13

Re: [PATCH 03/12] filemap: update ki_pos in generic_perform_write

From: Al Viro <viro@zeniv.linux.org.uk>
Date: 2023-08-28 14:03:15
Also in: ceph-devel, linux-ext4, linux-f2fs-devel, linux-fsdevel, linux-mm, linux-nfs, linux-xfs

On Mon, Aug 28, 2023 at 02:30:23PM +0200, Christoph Hellwig wrote:
On Sun, Aug 27, 2023 at 08:41:22PM +0100, Al Viro wrote:
quoted
That part is somewhat fishy - there's a case where you return a positive value
and advance ->ki_pos by more than that amount.  I really wonder if all callers
of ->write_iter() are OK with that.  Consider e.g. this:
This should not exist in the latest version merged by Jens.  Can you
check if you still  see issues in the version in the block tree or
linux-next.
Still does - the problem has migrated into direct_write_fallback(), but
that hadn't changed the situation.  We are still left with ->ki_pos bumped
by generic_perform_write() (evaluated as an argument of direct_write_fallback()
now) and *not* retraced in case when direct_write_fallback() decides to
discard the buffered write result.  Both in -next and in mainline (since
6.5-rc1).
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help