From: "Darrick J. Wong" <djwong@kernel.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfs/232 crashing on 5.13-rc1?
Date: Thu, 13 May 2021 12:03:55 -0700 [thread overview]
Message-ID: <20210513190355.GA9610@magnolia> (raw)
Hi everyone,
Sorry if this has already been fixed somewhere else, but I noticed the
following crash in btrfs/232 on 5.13-rc1. It's not quite vanilla, but
the only changes to the kernel source are some unexciting xfs realtime
bug fixes:
run fstests btrfs/232 at 2021-05-12 19:53:40
BTRFS info (device sda3): disk space caching is enabled
BTRFS info (device sda3): has skinny extents
BTRFS: device fsid 83eea612-5b69-486e-9e29-b1e46742d469 devid 1 transid 5 /dev/sda4 scanned by mkfs.btrfs (1783608)
BTRFS info (device sda4): disk space caching is enabled
BTRFS info (device sda4): has skinny extents
BTRFS info (device sda4): flagging fs with big metadata feature
BTRFS info (device sda4): checking UUID tree
BTRFS warning (device sda4): qgroup rescan is already in progress
BTRFS info (device sda4): qgroup scan completed (inconsistency flag cleared)
BUG: unable to handle page fault for address: ffffffffffffff86
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 43f010067 P4D 43f010067 PUD 43f012067 PMD 0
Oops: 0000 [#1] PREEMPT SMP NOPTI
CPU: 0 PID: 1783648 Comm: fsstress Not tainted 5.13.0-rc1-xfsx #rc1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS ?-20171121_152543-x86-ol7-builder-01.us.oracle.com-4.el7.1 04/01/2014
RIP: 0010:btrfs_update_root_times+0x3a/0x90 [btrfs]
Code: 8d a3 98 04 00 00 48 83 ec 18 65 48 8b 04 25 28 00 00 00 48 89 44 24 10 31 c0 48 89 e7 e8 be d0 b7 e0 4c 89 e7 e8 76 c1 19 e1 <48> 8b 45 00 4c 89 e7 48 89 83 4f 01 00 00 48 8b 04 24 48 89 83 6f
RSP: 0018:ffffc90002e57d88 EFLAGS: 00010246
RAX: ffff888102513e80 RBX: ffff888142406000 RCX: 0000000000000017
RDX: 0000000000000001 RSI: 00000000001623ac RDI: ffff888142406498
RBP: ffffffffffffff86 R08: 0017b8ff80000000 R09: 0000000000000005
R10: 0000000000000000 R11: ffff88810479ee30 R12: ffff888142406498
R13: ffffffffffffff86 R14: ffff8882f393e548 R15: 0000000000000000
FS: 00007f3872c9d740(0000) GS:ffff88843fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffff86 CR3: 000000016afce000 CR4: 00000000001506b0
Call Trace:
btrfs_update_inode+0x8e/0x100 [btrfs]
btrfs_fileattr_set+0x282/0x470 [btrfs]
vfs_fileattr_set+0x21e/0x260
do_vfs_ioctl+0xc9/0x920
__x64_sys_ioctl+0x3d/0xa0
do_syscall_64+0x3a/0x70
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7f3872db750b
Code: 0f 1e fa 48 8b 05 85 39 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 55 39 0d 00 f7 d8 64 89 01 48
RSP: 002b:00007fff626c66b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000010 RCX: 00007f3872db750b
RDX: 00007fff626c6770 RSI: 00000000401c5820 RDI: 0000000000000004
RBP: 0000000000000004 R08: 0000000000000048 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: 00000000000002de
R13: 0000000000000000 R14: 00007fff626c6770 R15: 000055df450225e0
Modules linked in: ext4 mbcache jbd2 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio dm_flakey btrfs xt_REDIRECT iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 ip_set_hash_ip ip_set_hash_net auth_rpcgss oid_registry xt_tcpudp xt_set ip_set_hash_mac blake2b_generic xor zstd_decompress zstd_compress lzo_compress lzo_decompress zlib_deflate ip_set nfnetlink ip6table_filter ip6_tables raid6_pq libcrc32c iptable_filter sch_fq_codel ip_tables x_tables overlay nfsv4 af_packet [last unloaded: scsi_debug]
Dumping ftrace buffer:
(ftrace buffer empty)
CR2: ffffffffffffff86
---[ end trace 4d6b79bcb0d4bd5f ]---
--D
next reply other threads:[~2021-05-13 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 19:03 Darrick J. Wong [this message]
2021-05-13 19:13 ` btrfs/232 crashing on 5.13-rc1? riteshh
2021-05-13 20:51 ` David Sterba
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=20210513190355.GA9610@magnolia \
--to=djwong@kernel.org \
--cc=linux-btrfs@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.