mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+f57a59b585e797d8c9b8@syzkaller.appspotmail.com>
To: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	 kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org,  pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: [syzbot] [net?] BUG: corrupted list in nsim_bpf_destroy_prog
Date: Thu, 14 Nov 2024 09:04:24 -0800	[thread overview]
Message-ID: <67362d98.050a0220.1324f8.009b.GAE@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    252e01e68241 selftests: net: add netlink-dumps to .gitignore
git tree:       net
console output: https://syzkaller.appspot.com/x/log.txt?x=157ce35f980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=64aa0d9945bd5c1
dashboard link: https://syzkaller.appspot.com/bug?extid=f57a59b585e797d8c9b8
compiler:       Debian clang version 15.0.6, 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/2459f940e3b8/disk-252e01e6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6b3823596aaa/vmlinux-252e01e6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bf011fb97648/bzImage-252e01e6.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f57a59b585e797d8c9b8@syzkaller.appspotmail.com

list_del corruption. prev->next should be ffff8880334808a8, but was ffff88805f2f43c0. (prev=ffff88805f2f43c0)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:64!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 8 Comm: kworker/0:0 Not tainted 6.12.0-rc6-syzkaller-00169-g252e01e68241 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Workqueue: events bpf_prog_free_deferred
RIP: 0010:__list_del_entry_valid_or_report+0x11b/0x140 lib/list_debug.c:62
Code: 00 07 90 0f 0b 48 c7 c7 a0 0d 61 8c 4c 89 fe e8 0b 8f 00 07 90 0f 0b 48 c7 c7 00 0e 61 8c 4c 89 fe 48 89 d9 e8 f6 8e 00 07 90 <0f> 0b 48 c7 c7 80 0e 61 8c 4c 89 fe 4c 89 f1 e8 e1 8e 00 07 90 0f
RSP: 0018:ffffc900000d7a00 EFLAGS: 00010246
RAX: 000000000000006d RBX: ffff88805f2f43c0 RCX: 67b0c67390e66700
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900000d7b38 R08: ffffffff8174a18c R09: fffffbfff1cf9fd0
R10: dffffc0000000000 R11: fffffbfff1cf9fd0 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88805f2f43c0 R15: ffff8880334808a8
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c38e396 CR3: 000000006435a000 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]
 list_del include/linux/list.h:229 [inline]
 nsim_bpf_destroy_prog+0xd9/0x1f0 drivers/net/netdevsim/bpf.c:281
 __bpf_prog_offload_destroy kernel/bpf/offload.c:113 [inline]
 bpf_prog_dev_bound_destroy+0x2aa/0x590 kernel/bpf/offload.c:392
 bpf_prog_free_deferred+0x3c5/0x710 kernel/bpf/core.c:2796
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa63/0x1850 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/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+0x11b/0x140 lib/list_debug.c:62
Code: 00 07 90 0f 0b 48 c7 c7 a0 0d 61 8c 4c 89 fe e8 0b 8f 00 07 90 0f 0b 48 c7 c7 00 0e 61 8c 4c 89 fe 48 89 d9 e8 f6 8e 00 07 90 <0f> 0b 48 c7 c7 80 0e 61 8c 4c 89 fe 4c 89 f1 e8 e1 8e 00 07 90 0f
RSP: 0018:ffffc900000d7a00 EFLAGS: 00010246
RAX: 000000000000006d RBX: ffff88805f2f43c0 RCX: 67b0c67390e66700
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900000d7b38 R08: ffffffff8174a18c R09: fffffbfff1cf9fd0
R10: dffffc0000000000 R11: fffffbfff1cf9fd0 R12: dffffc0000000000
R13: dffffc0000000000 R14: ffff88805f2f43c0 R15: ffff8880334808a8
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f8c75d062d8 CR3: 0000000064358000 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-11-14 17:04 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=67362d98.050a0220.1324f8.009b.GAE@google.com \
    --to=syzbot+f57a59b585e797d8c9b8@syzkaller.appspotmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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

all inboxes | Powered by JetHome®