> On Jun 26, 2022, at 2:05 PM, Anthony Joseph Messina <amessina@xxxxxxxxxxxx> wrote: > > On Sunday, June 26, 2022 6:15:39 AM CDT Zorro Lang wrote: >> On Mon, Jun 20, 2022 at 02:21:14PM +0800, Zorro Lang wrote: >>> Hi, >>> >>> I hit kernel panic and KASAN BUG [1] on NFS over XFS, I've left more >>> details in bugzilla, refer to: >>> https://bugzilla.kernel.org/show_bug.cgi?id=216151 >>> >>> The kernel commit HEAD is 05c6ca8512f2722f57743d653bb68cf2a273a55a, which >>> contains xfs-5.19-fixes-1. >>> >>> Not sure if it's NFS or XFS issue, so cc both mail list. >> >> It's still reproducible on my regression test of this week, on linux >> 5.19.0-rc3+ (HEAD=92f20ff72066d8d7e2ffb655c2236259ac9d1c5d). >> >> And the feedback from Dave (XFS side) said it doesn't like a XFS issue: >> https://bugzilla.kernel.org/show_bug.cgi?id=216151#c3 >> >> Can NFS devel help to take a look? >> >> Thanks, >> Zorro > > Not being a developer, I can't be sure it's directly related, but in the > 5.18.x series (Fedora 36) kernels, I experience NFSD/XFS failures (with > associated data loss) reported here: > > https://bugzilla.redhat.com/show_bug.cgi?id=2100859 I don't see READ_PLUS-related functions in any of those call traces, and the OP in this email thread does not report filesystem corruption. So IMHO RH 2100859 does not appear to be directly related to 216151. -- Chuck Lever
