From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 216566] [xfstests generic/648] BUG: unable to handle page fault, RIP: 0010:__xfs_dir3_data_check+0x171/0x700 [xfs]
Date: Mon, 10 Oct 2022 01:31:40 +0000 [thread overview]
Message-ID: <bug-216566-201763-CsVSUutBIa@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216566-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216566
--- Comment #2 from Zorro Lang (zlang@redhat.com) ---
(In reply to Dave Chinner from comment #1)
> On Sun, Oct 09, 2022 at 05:47:49PM +0000, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=216566
> >
> > Bug ID: 216566
> > Summary: [xfstests generic/648] BUG: unable to handle page
> > fault, RIP: 0010:__xfs_dir3_data_check+0x171/0x700
> > [xfs]
> > Product: File System
> > Version: 2.5
> > Kernel Version: v6.1-rc0
> > Hardware: All
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: XFS
> > Assignee: filesystem_xfs@kernel-bugs.kernel.org
> > Reporter: zlang@redhat.com
> > Regression: No
> >
> > xfstests generic/648 hit kernel panic[1] on xfs with 64k directory block
> size
> > (-n size=65536), before panic, there's a kernel assertion (not sure if it's
> > related).
> >
> > It's reproducable, but not easy. Generally I reproduced it by loop running
> > generic/648 on xfs (-n size=65536) hundreds of time.
> >
> > The last time I hit this panic on linux with HEAD=
>
> Given that there have been no changes to XFS committed in v6.1-rc0
> at this point in time, this won't be an XFS regression unless you
> can reproduce it on 6.0 or 5.19 kernels, too. Regardless, I'd suggest
> bisection is in order to find where the problem was introduced.
It's not a regression recently, I even can reproduce it on RHEL-9 (which base
on 5.14 kernel).
>
> -Dave.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-10-10 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 17:47 [Bug 216566] New: [xfstests generic/648] BUG: unable to handle page fault, RIP: 0010:__xfs_dir3_data_check+0x171/0x700 [xfs] bugzilla-daemon
2022-10-09 22:47 ` Dave Chinner
2022-10-09 22:47 ` [Bug 216566] " bugzilla-daemon
2022-10-10 1:31 ` bugzilla-daemon [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=bug-216566-201763-CsVSUutBIa@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-xfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.