All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 215804] New: [xfstests generic/670] Unable to handle kernel paging request at virtual address fffffbffff000008
Date: Tue, 05 Apr 2022 04:44:35 +0000	[thread overview]
Message-ID: <bug-215804-201763@https.bugzilla.kernel.org/> (raw)

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):

The kernel version is linux 5.17+ (nearly 5.18-rc1, contains latest
xfs-5.18-merge-4)
The linux kernel HEAD is (nearly 5.18-rc1, but not):

commit be2d3ecedd9911fbfd7e55cc9ceac5f8b79ae4cf
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sat Apr 2 12:57:17 2022 -0700

    Merge tag 'perf-tools-for-v5.18-2022-04-02' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux

[1]
[37277.345917] run fstests generic/670 at 2022-04-03 17:02:54 
[37278.883000] XFS (vda3): Mounting V5 Filesystem 
[37278.891732] XFS (vda3): Ending clean mount 
[37278.920425] XFS (vda3): Unmounting Filesystem 
[37279.399805] XFS (vda3): Mounting V5 Filesystem 
[37279.407734] XFS (vda3): Ending clean mount 
[37280.068575] XFS (vda3): Unmounting Filesystem 
[37280.399733] XFS (vda3): Mounting V5 Filesystem 
[37280.410122] XFS (vda3): Ending clean mount 
[37285.232165] Unable to handle kernel paging request at virtual address
fffffbffff000008 
[37285.232776] KASAN: maybe wild-memory-access in range
[0x0003dffff8000040-0x0003dffff8000047] 
[37285.233332] Mem abort info: 
[37285.233520]   ESR = 0x96000006 
[37285.233725]   EC = 0x25: DABT (current EL), IL = 32 bits 
[37285.234077]   SET = 0, FnV = 0 
[37285.234281]   EA = 0, S1PTW = 0 
[37285.234544]   FSC = 0x06: level 2 translation fault 
[37285.234871] Data abort info: 
[37285.235065]   ISV = 0, ISS = 0x00000006 
[37285.235319]   CM = 0, WnR = 0 
[37285.235517] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000004574eb000 
[37285.235953] [fffffbffff000008] pgd=0000000458c71003, p4d=0000000458c71003,
pud=0000000458c72003, pmd=0000000000000000 
[37285.236651] Internal error: Oops: 96000006 [#1] SMP 
[37285.236971] Modules linked in: overlay dm_zero dm_log_writes dm_thin_pool
dm_persistent_data dm_bio_prison sg dm_snapshot dm_bufio ext4 mbcache jbd2 loop
dm_flakey dm_mod tls rfkill sunrpc vfat fat drm fuse xfs libcrc32c crct10dif_ce
ghash_ce virtio_blk sha2_ce sha256_arm64 sha1_ce virtio_console virtio_net
net_failover failover virtio_mmio [last unloaded: scsi_debug] 
[37285.239187] CPU: 3 PID: 3302514 Comm: xfs_io Kdump: loaded Tainted: G       
W         5.17.0+ #1 
[37285.239810] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 
[37285.240292] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) 
[37285.240783] pc : __split_huge_pmd+0x1d8/0x34c 
[37285.241097] lr : __split_huge_pmd+0x174/0x34c 
[37285.241407] sp : ffff800023a56fe0 
[37285.241642] x29: ffff800023a56fe0 x28: 0000000000000000 x27:
ffff0001c54d4060 
[37285.242145] x26: 0000000000000000 x25: 0000000000000000 x24:
fffffc00056cf000 
[37285.242661] x23: 1ffff0000474ae0a x22: ffff0007104fe630 x21:
ffff00014fab66b0 
[37285.243175] x20: ffff800023a57080 x19: fffffbffff000000 x18:
0000000000000000 
[37285.243689] x17: 0000000000000000 x16: ffffb109a2ec7e30 x15:
0000ffffd9035c10 
[37285.244202] x14: 00000000f2040000 x13: 0000000000000000 x12:
ffff70000474aded 
[37285.244715] x11: 1ffff0000474adec x10: ffff70000474adec x9 :
dfff800000000000 
[37285.245230] x8 : ffff800023a56f63 x7 : 0000000000000001 x6 :
0000000000000003 
[37285.245745] x5 : ffff800023a56f60 x4 : ffff70000474adec x3 :
1fffe000cd086e01 
[37285.246257] x2 : 1fffff7fffe00001 x1 : 0000000000000000 x0 :
fffffbffff000008 
[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 
[37285.249812]  xfs_flush_unmap_range+0xc8/0x10c [xfs] 
[37285.250316]  xfs_reflink_remap_prep+0x2f4/0x3ac [xfs] 
[37285.250822]  xfs_file_remap_range+0x170/0x770 [xfs] 
[37285.251314]  do_clone_file_range+0x198/0x5e0 
[37285.251629]  vfs_clone_file_range+0xa8/0x63c 
[37285.251942]  ioctl_file_clone+0x5c/0xc0 
[37285.252232]  do_vfs_ioctl+0x10d4/0x1684 
[37285.252517]  __arm64_sys_ioctl+0xcc/0x18c 
[37285.252813]  invoke_syscall.constprop.0+0x74/0x1e0 
[37285.253166]  el0_svc_common.constprop.0+0x224/0x2c0 
[37285.253525]  do_el0_svc+0xa4/0xf0 
[37285.253769]  el0_svc+0x5c/0x160 
[37285.254002]  el0t_64_sync_handler+0x9c/0x120 
[37285.254312]  el0t_64_sync+0x174/0x178 
[37285.254584] Code: 91002260 d343fc02 38e16841 35000b41 (f9400660)  
[37285.255026] SMP: stopping secondary CPUs 
[37285.292297] Starting crashdump kernel... 
[37285.292706] Bye! 
[    0.000000] Booting Linux on physical CPU 0x0000000003 [0x413fd0c1]

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-04-05  4:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05  4:44 bugzilla-daemon [this message]
2022-04-05  4:48 ` [Bug 215804] [xfstests generic/670] Unable to handle kernel paging request at virtual address fffffbffff000008 bugzilla-daemon
2022-04-05  5:13 ` bugzilla-daemon
2022-04-05  5:26 ` [Bug 215804] New: " Dave Chinner
2022-04-05  5:27 ` [Bug 215804] " bugzilla-daemon
2022-04-05 16:27 ` 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@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.