From: syzbot <syzbot+df3f3ef31f60781fa911@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] BUG: corrupted list in ptp_open
Date: Fri, 27 Oct 2023 19:55:05 -0700 [thread overview]
Message-ID: <000000000000a318600608bdee98@google.com> (raw)
In-Reply-To: <20231028011908.956-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: corrupted list in ptp_release
list_del corruption. prev->next should be ffff88806d1f9048, but was ffff88814ad945e8. (prev=ffff88814ad99048)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:62!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 9040 Comm: syz-executor.1 Not tainted 6.6.0-rc6-next-20231020-syzkaller-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:__list_del_entry_valid_or_report+0x11f/0x1b0 lib/list_debug.c:62
Code: 9f e9 8a e8 c3 a3 3a fd 0f 0b 48 89 ca 48 c7 c7 c0 9f e9 8a e8 b2 a3 3a fd 0f 0b 48 89 c2 48 c7 c7 20 a0 e9 8a e8 a1 a3 3a fd <0f> 0b 48 89 d1 48 c7 c7 a0 a0 e9 8a 48 89 c2 e8 8d a3 3a fd 0f 0b
RSP: 0018:ffffc90009f37e08 EFLAGS: 00010086
RAX: 000000000000006d RBX: ffff88806d1f8000 RCX: ffffffff816bb8d9
RDX: 0000000000000000 RSI: ffffffff816c4d42 RDI: 0000000000000005
RBP: ffff88807dbfcbe0 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000001 R12: 0000000000000246
R13: ffff88806d1f9048 R14: ffff88806d1f9008 R15: ffff88806d1f9050
FS: 0000555556b75480(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fec1cd98000 CR3: 00000000263b9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__list_del_entry_valid include/linux/list.h:124 [inline]
__list_del_entry include/linux/list.h:215 [inline]
list_del include/linux/list.h:229 [inline]
ptp_release+0xc4/0x2b0 drivers/ptp/ptp_chardev.c:150
posix_clock_release+0xa4/0x160 kernel/time/posix-clock.c:157
__fput+0x270/0xbb0 fs/file_table.c:394
__fput_sync+0x47/0x50 fs/file_table.c:475
__do_sys_close fs/open.c:1590 [inline]
__se_sys_close fs/open.c:1575 [inline]
__x64_sys_close+0x86/0xf0 fs/open.c:1575
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:82
entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7fec1cc7b9da
Code: 48 3d 00 f0 ff ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 03 7f 02 00 8b 7c 24 0c 89 c2 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 36 89 d7 89 44 24 0c e8 63 7f 02 00 8b 44 24
RSP: 002b:00007ffc3d751870 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fec1cc7b9da
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003
RBP: 0000000000000032 R08: 0000001b2df60000 R09: 00007fec1cd9bf8c
R10: 00007ffc3d7519c0 R11: 0000000000000293 R12: 00007fec1c8000a8
R13: ffffffffffffffff R14: 00007fec1c800000 R15: 0000000000028903
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0x11f/0x1b0 lib/list_debug.c:62
Code: 9f e9 8a e8 c3 a3 3a fd 0f 0b 48 89 ca 48 c7 c7 c0 9f e9 8a e8 b2 a3 3a fd 0f 0b 48 89 c2 48 c7 c7 20 a0 e9 8a e8 a1 a3 3a fd <0f> 0b 48 89 d1 48 c7 c7 a0 a0 e9 8a 48 89 c2 e8 8d a3 3a fd 0f 0b
RSP: 0018:ffffc90009f37e08 EFLAGS: 00010086
RAX: 000000000000006d RBX: ffff88806d1f8000 RCX: ffffffff816bb8d9
RDX: 0000000000000000 RSI: ffffffff816c4d42 RDI: 0000000000000005
RBP: ffff88807dbfcbe0 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000001 R12: 0000000000000246
R13: ffff88806d1f9048 R14: ffff88806d1f9008 R15: ffff88806d1f9050
FS: 0000555556b75480(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fec1cd98000 CR3: 00000000263b9000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Tested on:
commit: 20305791 Add linux-next specific files for 20231020
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=16c52007680000
kernel config: https://syzkaller.appspot.com/x/.config?x=37404d76b3c8840e
dashboard link: https://syzkaller.appspot.com/bug?extid=df3f3ef31f60781fa911
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17bc6cfd680000
next parent reply other threads:[~2023-10-28 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231028011908.956-1-hdanton@sina.com>
2023-10-28 2:55 ` syzbot [this message]
[not found] <tencent_77D0E91EEE8ECDB47BF26C5C2FFD6E68960A@qq.com>
2023-11-06 14:40 ` [syzbot] [net?] BUG: corrupted list in ptp_open syzbot
[not found] <tencent_E146F1D2D4464049842EEEEEE24C8EA7C306@qq.com>
2023-11-06 13:38 ` syzbot
[not found] <tencent_564ACA75C777AD66F83C0D370896CA360E09@qq.com>
2023-11-06 13:26 ` syzbot
[not found] <tencent_C16C882E596CC49668E85AECB6CD307BC60A@qq.com>
2023-11-05 2:06 ` syzbot
[not found] <tencent_C46D83B2044E376BB76286CF937A63682905@qq.com>
2023-11-05 1:35 ` syzbot
[not found] <tencent_42EB25AE0D8292425D8CDD9119714FA30D07@qq.com>
2023-11-04 3:13 ` syzbot
[not found] <tencent_C32CC16DCC9600E83EEC5ECC707B066C480A@qq.com>
2023-11-03 11:56 ` syzbot
[not found] <20231028113238.1092-1-hdanton@sina.com>
2023-10-28 11:57 ` syzbot
[not found] <20231028071018.1016-1-hdanton@sina.com>
2023-10-28 8:08 ` syzbot
2023-10-26 14:20 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=000000000000a318600608bdee98@google.com \
--to=syzbot+df3f3ef31f60781fa911@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 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.