From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 215804] [xfstests generic/670] Unable to handle kernel paging request at virtual address fffffbffff000008
Date: Tue, 05 Apr 2022 05:27:07 +0000 [thread overview]
Message-ID: <bug-215804-201763-yvs5Nhy9fK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215804-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215804
--- Comment #3 from Dave Chinner (david@fromorbit.com) ---
Hi Zorro,
On Tue, Apr 05, 2022 at 04:44:35AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215804
>
> Bug ID: 215804
> Summary: [xfstests generic/670] Unable to handle kernel paging
> request at virtual address fffffbffff000008
> Product: File System
> Version: 2.5
> Kernel Version: xfs-5.18-merge-4
> 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/670 hit a panic[1] on 64k directory block size XFS (mkfs.xfs
> -n size=65536 -m rmapbt=1 -b size=1024):
.....
> [37285.246770] Call trace:
> [37285.246952] __split_huge_pmd+0x1d8/0x34c
> [37285.247246] split_huge_pmd_address+0x10c/0x1a0
> [37285.247577] try_to_unmap_one+0xb64/0x125c
> [37285.247878] rmap_walk_file+0x1dc/0x4b0
> [37285.248159] try_to_unmap+0x134/0x16c
> [37285.248427] split_huge_page_to_list+0x5ec/0xcbc
> [37285.248763] truncate_inode_partial_folio+0x194/0x2ec
> [37285.249128] truncate_inode_pages_range+0x2e8/0x870
> [37285.249483] truncate_pagecache_range+0xa0/0xc0
That doesn't look like an XFS regression, more likely a bug in the
new large folios in the page cache feature. Can you revert commit
6795801366da ("xfs: Support large folios") and see if the problem
goes away?
Cheers,
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.
next prev parent reply other threads:[~2022-04-05 5:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 4:44 [Bug 215804] New: [xfstests generic/670] Unable to handle kernel paging request at virtual address fffffbffff000008 bugzilla-daemon
2022-04-05 4:48 ` [Bug 215804] " bugzilla-daemon
2022-04-05 5:13 ` bugzilla-daemon
2022-04-05 5:26 ` [Bug 215804] New: " Dave Chinner
2022-04-05 5:27 ` bugzilla-daemon [this message]
2022-04-05 16:27 ` [Bug 215804] " bugzilla-daemon
2022-04-05 19:23 ` [Bug 215804] New: " Matthew Wilcox
2022-04-05 20:48 ` Yang Shi
2022-04-05 19:23 ` [Bug 215804] " bugzilla-daemon
2022-04-05 20:48 ` bugzilla-daemon
2022-04-05 22:57 ` bugzilla-daemon
2022-04-06 4:32 ` bugzilla-daemon
2022-04-06 12:57 ` bugzilla-daemon
2022-04-07 2:18 ` bugzilla-daemon
2022-04-07 2:33 ` bugzilla-daemon
2022-04-07 2:54 ` bugzilla-daemon
2022-04-08 18:54 ` bugzilla-daemon
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-215804-201763-yvs5Nhy9fK@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).