From: Joel Granados <joel.granados@kernel.org>
To: Xingyu Li <xli399@ucr.edu>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, linux@weissschuh.net,
judyhsiao@chromium.org, James.Z.Li@dell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Yu Hao <yhao016@ucr.edu>
Subject: Re: BUG: corrupted list in neigh_parms_release
Date: Mon, 7 Oct 2024 22:21:39 +0200 [thread overview]
Message-ID: <20241007202139.f5mccuwwuexuvtle@joelS2.panther.com> (raw)
In-Reply-To: <CALAgD-7NTOZ-8-uLbRSa35B+wKkXzzmviE1hy6ajLxwU2kfj7Q@mail.gmail.com>
On Wed, Aug 28, 2024 at 04:36:00PM -0700, Xingyu Li wrote:
> Hi,
>
> We found a bug in Linux 6.10 using syzkaller. It is possibly a
> corrupted list bug.
> The bug report is as follows, but unfortunately there is no generated
> syzkaller reproducer.
Sorry for the late reply. Please resend when you find a reproducer.
>
> Bug report:
>
> list_del corruption. next->prev should be ffff88801b3bdc18, but was
> 0000000000000000. (next=ffff88803c7c5018)
> ------------[ cut here ]------------
> kernel BUG at lib/list_debug.c:67!
> Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
> CPU: 0 PID: 47298 Comm: kworker/u4:24 Not tainted 6.10.0 #13
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
> Workqueue: netns cleanup_net
> RIP: 0010:__list_del_entry_valid_or_report+0x11e/0x120 lib/list_debug.c:65
> Code: 96 06 0f 0b 48 c7 c7 e0 5b a9 8b 4c 89 fe 48 89 d9 e8 96 ff 96
> 06 0f 0b 48 c7 c7 60 5c a9 8b 4c 89 fe 4c 89 f1 e8 82 ff 96 06 <0f> 0b
> 80 3d bd 35 c6 0a 00 74 01 c3 31 d2 eb 02 66 90 55 41 57 41
> RSP: 0018:ffffc90002aff6b8 EFLAGS: 00010246
> RAX: 000000000000006d RBX: ffff88803c7c5020 RCX: 1547a0d62a403a00
> RDX: 0000000000000000 RSI: 0000000080000201 RDI: 0000000000000000
> RBP: ffffffff8ee71680 R08: ffffffff8172e30c R09: 1ffff9200055fe78
> R10: dffffc0000000000 R11: fffff5200055fe79 R12: dffffc0000000000
> R13: dffffc0000000000 R14: ffff88803c7c5018 R15: ffff88801b3bdc18
> FS: 0000000000000000(0000) GS:ffff888063a00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f6cc5e4f360 CR3: 00000000413bc000 CR4: 0000000000350ef0
> 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]
> neigh_parms_release+0x51/0x230 net/core/neighbour.c:1759
> addrconf_ifdown+0x188c/0x1b50 net/ipv6/addrconf.c:4009
> addrconf_notify+0x3c4/0x1000
> notifier_call_chain kernel/notifier.c:93 [inline]
> raw_notifier_call_chain+0xe0/0x180 kernel/notifier.c:461
> call_netdevice_notifiers_extack net/core/dev.c:2030 [inline]
> call_netdevice_notifiers net/core/dev.c:2044 [inline]
> unregister_netdevice_many_notify+0xd65/0x16d0 net/core/dev.c:11219
> cleanup_net+0x764/0xcd0 net/core/net_namespace.c:635
> process_one_work kernel/workqueue.c:3248 [inline]
> process_scheduled_works+0x977/0x1410 kernel/workqueue.c:3329
> worker_thread+0xaa0/0x1020 kernel/workqueue.c:3409
> kthread+0x2eb/0x380 kernel/kthread.c:389
> ret_from_fork+0x49/0x80 arch/x86/kernel/process.c:147
> ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:244
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:__list_del_entry_valid_or_report+0x11e/0x120 lib/list_debug.c:65
> Code: 96 06 0f 0b 48 c7 c7 e0 5b a9 8b 4c 89 fe 48 89 d9 e8 96 ff 96
> 06 0f 0b 48 c7 c7 60 5c a9 8b 4c 89 fe 4c 89 f1 e8 82 ff 96 06 <0f> 0b
> 80 3d bd 35 c6 0a 00 74 01 c3 31 d2 eb 02 66 90 55 41 57 41
> RSP: 0018:ffffc90002aff6b8 EFLAGS: 00010246
> RAX: 000000000000006d RBX: ffff88803c7c5020 RCX: 1547a0d62a403a00
> RDX: 0000000000000000 RSI: 0000000080000201 RDI: 0000000000000000
> RBP: ffffffff8ee71680 R08: ffffffff8172e30c R09: 1ffff9200055fe78
> R10: dffffc0000000000 R11: fffff5200055fe79 R12: dffffc0000000000
> R13: dffffc0000000000 R14: ffff88803c7c5018 R15: ffff88801b3bdc18
> FS: 0000000000000000(0000) GS:ffff888063a00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f6cc5e4f360 CR3: 00000000413bc000 CR4: 0000000000350ef0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
>
>
> --
> Yours sincerely,
> Xingyu
--
Joel Granados
prev parent reply other threads:[~2024-10-07 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 23:36 Xingyu Li
2024-10-07 20:21 ` Joel Granados [this message]
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=20241007202139.f5mccuwwuexuvtle@joelS2.panther.com \
--to=joel.granados@kernel.org \
--cc=James.Z.Li@dell.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=judyhsiao@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xli399@ucr.edu \
--cc=yhao016@ucr.edu \
/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®