linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Anthony Joseph Messina <amessina@messinet.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Zorro Lang <zlang@kernel.org>,
	"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [Bug report] fstests g/465 panic on NFS over XFS (linux v5.19-rc2+)
Date: Sun, 26 Jun 2022 20:59:24 +0000	[thread overview]
Message-ID: <5CFCCD64-FACC-4256-A0CB-0A69ECF868D3@oracle.com> (raw)
In-Reply-To: <12005337.O9o76ZdvQC@linux-ws1.messinet.com>


> On Jun 26, 2022, at 2:05 PM, Anthony Joseph Messina <amessina@messinet.com> 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





      reply	other threads:[~2022-06-26 20:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  6:21 Zorro Lang
2022-06-26 11:15 ` Zorro Lang
2022-06-26 17:04   ` Chuck Lever III
2022-06-26 18:05   ` Anthony Joseph Messina
2022-06-26 20:59     ` Chuck Lever III [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=5CFCCD64-FACC-4256-A0CB-0A69ECF868D3@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=amessina@messinet.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@kernel.org \
    /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