From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 217171] ext4: stale buffer loading from last failed mounting
Date: Fri, 10 Mar 2023 12:37:37 +0000 [thread overview]
Message-ID: <bug-217171-13602-ocMIEJvL6b@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217171-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217171
--- Comment #1 from Zhihao Cheng (chengzhihao1@huawei.com) ---
1. Apply main_diff
2. sh test.sh
[ 116.709224] mount sda
[ 116.711840] load bh ffff88817b33edd0
[ 116.712425] inject
[ 116.712681] JBD2: recovery failed
[ 116.713067] EXT4-fs (sda): error loading journal
[ 116.731617] mount sda
[ 116.732129] found stale bh ffff88817b33edd0 # stale buffer head from last
failed mounting
[ 116.732713] Kernel panic - not syncing: not verified
[ 116.733366] CPU: 3 PID: 2613 Comm: mount Not tainted
6.3.0-rc1-00003-g737d811674e8-dirty #1125
[ 116.734528] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
?-20190727_073836-buildvm-ppc64le-16.ppc.fedoraprojec4
[ 116.736052] Call Trace:
[ 116.736339] <TASK>
[ 116.736600] dump_stack_lvl+0x7f/0xb0
[ 116.736941] dump_stack+0x18/0x30
[ 116.737316] panic+0x4e6/0x520
[ 116.737719] journal_get_superblock+0x7dc/0x7e0
[ 116.738285] load_superblock+0x16/0x100
[ 116.738713] jbd2_journal_wipe+0x2c/0x140
[ 116.739138] ? ext4_init_journal_params+0xa0/0xe0
[ 116.739668] ext4_load_and_init_journal.isra.0+0x8df/0x11c0
[ 116.740291] ? _printk+0x64/0x90
[ 116.740617] __ext4_fill_super+0x2a15/0x3370
[ 116.741098] ? __ext4_fill_super+0x3370/0x3370
[ 116.741667] ext4_fill_super+0x121/0x2f0
[ 116.742073] get_tree_bdev+0x1d6/0x370
[ 116.742493] ext4_get_tree+0x1d/0x30
[ 116.742922] vfs_get_tree+0x2a/0x110
[ 116.743357] ? capable+0x21/0x30
[ 116.743701] path_mount+0x821/0xfc0
[ 116.744077] do_mount+0x91/0xc0
[ 116.744480] __x64_sys_mount+0xc4/0x160
[ 116.744906] do_syscall_64+0x39/0x80
[ 116.745300] entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 116.745838] RIP: 0033:0x7fc8f931123a
[ 116.746350] Code: 48 8b 0d 51 dc 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e
0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b88
[ 116.748348] RSP: 002b:00007fffdb903258 EFLAGS: 00000202 ORIG_RAX:
00000000000000a5
[ 116.749172] RAX: ffffffffffffffda RBX: 0000000000733240 RCX:
00007fc8f931123a
[ 116.749996] RDX: 0000000000739f90 RSI: 00000000007334a0 RDI:
0000000000733480
[ 116.750801] RBP: 0000000000000000 R08: 0000000000000000 R09:
00007fffdb9021c8
[ 116.751565] R10: 0000000000000000 R11: 0000000000000202 R12:
0000000000733480
[ 116.752372] R13: 0000000000739f90 R14: 0000000000000001 R15:
0000000000733240
[ 116.753137] </TASK>
[ 116.753498] Kernel Offset: disabled
[ 116.753822] ---[ end Kernel panic - not syncing: not verified ]---
--
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:[~2023-03-10 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 12:35 [Bug 217171] New: ext4: stale buffer loading from last failed mounting bugzilla-daemon
2023-03-10 12:37 ` bugzilla-daemon [this message]
2023-03-10 12:38 ` [Bug 217171] " bugzilla-daemon
2023-03-10 12:38 ` 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-217171-13602-ocMIEJvL6b@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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).