[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKPOu+96b4nx3iHaH6Mkf2GyJ-dr0i5o=hfFVDs--gWkN7aiDQ@mail.gmail.com>
Date: Fri, 29 Nov 2024 23:29:49 +0100
From: Max Kellermann <max.kellermann@...os.com>
To: David Howells <dhowells@...hat.com>
Cc: Jeff Layton <jlayton@...nel.org>, netfs@...ts.linux.dev,
linux-fsdevel <linux-fsdevel@...r.kernel.org>, linux-kernel@...r.kernel.org
Subject: Re: 6.12 WARNING in netfs_consume_read_data()
On Fri, Nov 29, 2024 at 1:41 PM David Howells <dhowells@...hat.com> wrote:
> Could you try:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=netfs-writeback
>
> I think the patches there should fix it.
I have encountered multiple hangs with that branch; for example:
[<0>] folio_wait_private_2_killable+0xfb/0x180
[<0>] netfs_write_begin+0xe0/0x450
[<0>] ceph_write_begin+0x27/0x50
[<0>] generic_perform_write+0xcd/0x280
[<0>] ceph_write_iter+0x4d9/0x640
[<0>] iter_file_splice_write+0x308/0x550
[<0>] splice_file_range_actor+0x29/0x40
[<0>] splice_direct_to_actor+0xee/0x270
[<0>] splice_file_range+0x80/0xc0
[<0>] ceph_copy_file_range+0xb5/0x5b0
[<0>] vfs_copy_file_range+0x320/0x5b0
[<0>] __x64_sys_copy_file_range+0xef/0x200
[<0>] do_syscall_64+0x64/0x100
[<0>] entry_SYSCALL_64_after_hwframe+0x76/0x7e
I can't be 100% sure if this was caused by your branch or if this is
just another 6.12 regression, but I haven't seen this with 6.11.
Powered by blists - more mailing lists