From: syzbot <syzbot+bb540a4bbfb4ae3b425d@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] INFO: task hung in rfkill_unregister (3)
Date: Sun, 30 Jul 2023 02:13:36 -0700 [thread overview]
Message-ID: <000000000000911a550601b0baa6@google.com> (raw)
In-Reply-To: <20230730084547.1164-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: corrupted list in nfc_llcp_register_device
list_add corruption. next->prev should be prev (ffff800090c7cc20), but was dead000000000122. (next=ffff0000e3ceb000).
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:29!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 13850 Comm: syz-executor304 Not tainted 6.5.0-rc3-syzkaller-00297-gd31e3792919e-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __list_add_valid+0xf4/0x110 lib/list_debug.c:27
lr : __list_add_valid+0xf4/0x110 lib/list_debug.c:27
sp : ffff80009ec57320
x29: ffff80009ec57320 x28: dfff800000000000 x27: 1fffe0001c79dc0d
x26: 1fffe00019d23801 x25: 1fffe00019d23800 x24: dfff800000000000
x23: dfff800000000000 x22: ffff0000e3ceb008 x21: ffff0000ce91c000
x20: ffff800090c7cc20 x19: ffff0000e3ceb000 x18: ffff80009ec56980
x17: 3032636337633039 x16: ffff80008a56521c x15: 0000000000000001
x14: 1ffff00013d8adbc x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000000 x10: 0000000000000000 x9 : 0b5847480dd8ce00
x8 : 0b5847480dd8ce00 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80009ec56c38 x4 : ffff80008e14ef00 x3 : ffff800082ad14b8
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000075
Call trace:
__list_add_valid+0xf4/0x110 lib/list_debug.c:27
__list_add include/linux/list.h:69 [inline]
list_add include/linux/list.h:88 [inline]
nfc_llcp_register_device+0x58c/0x6bc net/nfc/llcp_core.c:1639
nfc_register_device+0x88/0x2e4 net/nfc/core.c:1125
nci_register_device+0x6ac/0x7c4 net/nfc/nci/core.c:1257
virtual_ncidev_open+0x13c/0x1bc drivers/nfc/virtual_ncidev.c:148
misc_open+0x2f0/0x368 drivers/char/misc.c:165
chrdev_open+0x3e8/0x4fc fs/char_dev.c:414
do_dentry_open+0x710/0x11b8 fs/open.c:914
vfs_open+0x7c/0x90 fs/open.c:1048
do_open fs/namei.c:3636 [inline]
path_openat+0x1f2c/0x27f8 fs/namei.c:3793
do_filp_open+0x1bc/0x3cc fs/namei.c:3820
do_sys_openat2+0x124/0x1b8 fs/open.c:1407
do_sys_open fs/open.c:1422 [inline]
__do_sys_openat fs/open.c:1438 [inline]
__se_sys_openat fs/open.c:1433 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1433
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x244 arch/arm64/kernel/syscall.c:139
do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:188
el0_svc+0x4c/0x160 arch/arm64/kernel/entry-common.c:647
el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:665
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591
Code: 91098000 aa1403e1 aa1303e3 95e86b4d (d4210000)
---[ end trace 0000000000000000 ]---
Tested on:
commit: d31e3792 Merge tag '6.5-rc3-smb3-client-fixes' of git:..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=14847039a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=32bbbdc67cf060fa
dashboard link: https://syzkaller.appspot.com/bug?extid=bb540a4bbfb4ae3b425d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=142be711a80000
next parent reply other threads:[~2023-07-30 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230730084547.1164-1-hdanton@sina.com>
2023-07-30 9:13 ` syzbot [this message]
[not found] <20230730105902.1226-1-hdanton@sina.com>
2023-07-30 11:27 ` [syzbot] [wireless?] INFO: task hung in rfkill_unregister (3) syzbot
2023-06-07 9:58 syzbot
2023-06-07 10:22 ` Johannes Berg
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=000000000000911a550601b0baa6@google.com \
--to=syzbot+bb540a4bbfb4ae3b425d@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