From: syzbot <syzbot+e92661ab419d1a81b816@syzkaller.appspotmail.com>
To: jmorris@namei.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
penguin-kernel@I-love.SAKURA.ne.jp, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, takedakn@nttdata.co.jp,
tomoyo-dev-en@lists.osdn.me
Subject: [syzbot] [tomoyo?] BUG: corrupted list in tomoyo_try_to_gc
Date: Mon, 16 Dec 2024 01:53:22 -0800 [thread overview]
Message-ID: <675ff892.050a0220.37aaf.012a.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: f92f4749861b Merge tag 'clk-fixes-for-linus' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=132a7b30580000
kernel config: https://syzkaller.appspot.com/x/.config?x=99a5586995ec03b2
dashboard link: https://syzkaller.appspot.com/bug?extid=e92661ab419d1a81b816
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b85403132ddc/disk-f92f4749.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/20613d034287/vmlinux-f92f4749.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d1ea80bf7e4e/bzImage-f92f4749.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+e92661ab419d1a81b816@syzkaller.appspotmail.com
list_del corruption, ffff8880258fb100->next is NULL
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:52!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 9271 Comm: GC for TOMOYO Not tainted 6.13.0-rc2-syzkaller-00031-gf92f4749861b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__list_del_entry_valid_or_report+0xea/0x1c0 lib/list_debug.c:52
Code: 0f 85 ae 00 00 00 48 8b 42 08 48 39 c6 75 5f b8 01 00 00 00 48 83 c4 18 c3 cc cc cc cc 48 c7 c7 c0 59 b1 8b e8 67 f9 da fc 90 <0f> 0b 48 c7 c7 20 5a b1 8b e8 58 f9 da fc 90 0f 0b 48 c7 c7 80 5a
RSP: 0018:ffffc900041c7e00 EFLAGS: 00010282
RAX: 0000000000000033 RBX: ffff8880258fb100 RCX: ffffffff8178d119
RDX: 0000000000000000 RSI: ffffffff817978a6 RDI: 0000000000000005
RBP: ffff8880258fb100 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000001 R12: ffff8880258fb110
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000008
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555584206808 CR3: 000000007cd4a000 CR4: 00000000003526f0
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]
tomoyo_try_to_gc+0x21/0xcd0 security/tomoyo/gc.c:395
tomoyo_collect_entry security/tomoyo/gc.c:599 [inline]
tomoyo_gc_thread security/tomoyo/gc.c:619 [inline]
tomoyo_gc_thread+0xd3b/0x1390 security/tomoyo/gc.c:612
kthread+0x2c1/0x3a0 kernel/kthread.c:389
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0xea/0x1c0 lib/list_debug.c:52
Code: 0f 85 ae 00 00 00 48 8b 42 08 48 39 c6 75 5f b8 01 00 00 00 48 83 c4 18 c3 cc cc cc cc 48 c7 c7 c0 59 b1 8b e8 67 f9 da fc 90 <0f> 0b 48 c7 c7 20 5a b1 8b e8 58 f9 da fc 90 0f 0b 48 c7 c7 80 5a
RSP: 0018:ffffc900041c7e00 EFLAGS: 00010282
RAX: 0000000000000033 RBX: ffff8880258fb100 RCX: ffffffff8178d119
RDX: 0000000000000000 RSI: ffffffff817978a6 RDI: 0000000000000005
RBP: ffff8880258fb100 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000000 R11: 0000000000000001 R12: ffff8880258fb110
R13: dffffc0000000000 R14: 0000000000000000 R15: 0000000000000008
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555584206808 CR3: 000000007cd4a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-12-16 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=675ff892.050a0220.37aaf.012a.GAE@google.com \
--to=syzbot+e92661ab419d1a81b816@syzkaller.appspotmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takedakn@nttdata.co.jp \
--cc=tomoyo-dev-en@lists.osdn.me \
/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).