From: syzbot <syzbot+ea8b28e8dca42fc3bcbe@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: unable to handle kernel paging request in p9_client_disconnect
Date: Fri, 06 Jan 2023 20:08:33 -0800 [thread overview]
Message-ID: <0000000000000a5b5805f1a4b0c4@google.com> (raw)
In-Reply-To: <20230107020600.4739-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: unable to handle kernel paging request in p9_client_disconnect
Unable to handle kernel paging request at virtual address 0032503900080052
Mem abort info:
ESR = 0x0000000096000044
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
Data abort info:
ISV = 0, ISS = 0x00000044
CM = 0, WnR = 1
[0032503900080052] address between user and kernel address ranges
Internal error: Oops: 0000000096000044 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 3496 Comm: syz-executor.0 Not tainted 6.1.0-rc2-syzkaller-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : p9_client_disconnect+0x1c/0x30 net/9p/client.c:1067
lr : p9_client_disconnect+0x18/0x30 net/9p/client.c:1065
sp : ffff800010f83ca0
x29: ffff800010f83ca0 x28: ffff0000c684cec0 x27: 0000000000000000
x26: 00000000000000c0 x25: 0000000000000002 x24: ffff80000d37d050
x23: ffff80000d379000 x22: 0000000000000000 x21: 0000000000000000
x20: ffff0000cfaf5f00 x19: 3032503900080002 x18: 00000000000002aa
x17: ffff80000c0cd83c x16: 00000000000003fa x15: 0000000000000150
x14: 0000000001ef2008 x13: 0000000000000120 x12: 0000000000000000
x11: ff8080000be79558 x10: 0000000000000000 x9 : ffff80000be79558
x8 : 0000000000000002 x7 : 0000000000000000 x6 : ffff80000c036518
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : ffff0000c684cec0 x1 : 0000000000000000 x0 : 3032503900080002
Call trace:
p9_client_disconnect+0x1c/0x30
v9fs_session_cancel+0x2c/0x44 fs/9p/v9fs.c:534
v9fs_kill_super+0x2c/0x50 fs/9p/vfs_super.c:225
deactivate_locked_super+0x70/0xe8 fs/super.c:331
deactivate_super+0xd0/0xd4 fs/super.c:362
cleanup_mnt+0x184/0x1c0 fs/namespace.c:1186
__cleanup_mnt+0x20/0x30 fs/namespace.c:1193
task_work_run+0x100/0x148 kernel/task_work.c:179
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x174/0x1f0 arch/arm64/kernel/signal.c:1127
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x150 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:654
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
Code: 910003fd aa0003f3 9710b6ef 52800048 (b9005268)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 910003fd mov x29, sp
4: aa0003f3 mov x19, x0
8: 9710b6ef bl 0xfffffffffc42dbc4
c: 52800048 mov w8, #0x2 // #2
* 10: b9005268 str w8, [x19, #80] <-- trapping instruction
Tested on:
commit: 247f34f7 Linux 6.1-rc2
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=15b8a776480000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa9bed8d6a8992a0
dashboard link: https://syzkaller.appspot.com/bug?extid=ea8b28e8dca42fc3bcbe
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=17c64f3a480000
next parent reply other threads:[~2023-01-07 4:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230107020600.4739-1-hdanton@sina.com>
2023-01-07 4:08 ` syzbot [this message]
[not found] <20230107234052.5103-1-hdanton@sina.com>
2023-01-07 23:58 ` [syzbot] BUG: unable to handle kernel paging request in p9_client_disconnect syzbot
[not found] <20230107121634.4974-1-hdanton@sina.com>
2023-01-07 21:35 ` syzbot
[not found] <20230107063010.4809-1-hdanton@sina.com>
2023-01-07 7:01 ` syzbot
2022-11-22 15:35 syzbot
2023-01-06 5:38 ` syzbot
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=0000000000000a5b5805f1a4b0c4@google.com \
--to=syzbot+ea8b28e8dca42fc3bcbe@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/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