From: Xingyu Li <xli399@ucr.edu>
To: mcgrof@kernel.org, kees@kernel.org, j.granados@samsung.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: Yu Hao <yhao016@ucr.edu>
Subject: BUG: WARNING in retire_sysctl_set
Date: Wed, 28 Aug 2024 14:16:34 -0700 [thread overview]
Message-ID: <CALAgD-4uup-u-7rVLpFqKWqeVVVnf5-88vqHOKD-TnGeYmHbQw@mail.gmail.com> (raw)
Hi,
We found a bug in Linux 6.10. It is possibly a logic bug.
The bug report is as follows, but unfortunately there is no generated
syzkaller reproducer.
Bug report:
team0 (unregistering): Port device team_slave_1 removed
team0 (unregistering): Port device team_slave_0 removed
------------[ cut here ]------------
WARNING: CPU: 0 PID: 27 at fs/proc/proc_sysctl.c:1536
retire_sysctl_set+0x3e/0x50
Modules linked in:
CPU: 0 PID: 27 Comm: kworker/u4:2 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:retire_sysctl_set+0x3e/0x50 fs/proc/proc_sysctl.c:1536
Code: 48 b9 00 00 00 00 00 fc ff df 80 3c 08 00 74 08 48 89 df e8 44
a1 c6 ff 48 83 3b 00 75 07 e8 19 96 63 ff 5b c3 e8 12 96 63 ff <0f> 0b
5b c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 55 53 48 89
RSP: 0018:ffffc900001e7ad0 EFLAGS: 00010293
RAX: ffffffff822dbb4e RBX: ffff88801b87bc68 RCX: ffff8880137a3c00
RDX: 0000000000000000 RSI: ffff8880137a3c00 RDI: ffff88801b87bc08
RBP: ffffc900001e7bd0 R08: ffffffff910fc58f R09: 1ffffffff221f8b1
R10: dffffc0000000000 R11: ffffffff8ab261b0 R12: ffff88801b87b980
R13: 1ffffffff1e0aec8 R14: ffffffff8f057620 R15: ffffffff8f057640
FS: 0000000000000000(0000) GS:ffff888063a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005599fcd69b18 CR3: 000000003c258000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ops_exit_list net/core/net_namespace.c:173 [inline]
cleanup_net+0x810/0xcd0 net/core/net_namespace.c:640
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>
--
Yours sincerely,
Xingyu
next reply other threads:[~2024-08-28 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 21:16 Xingyu Li [this message]
2024-08-29 1:26 ` BUG: WARNING in retire_sysctl_set Kees Cook
2024-08-29 5:02 ` Xingyu Li
2024-08-29 5:33 ` Kees Cook
2024-08-29 6:00 ` Yu Hao
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=CALAgD-4uup-u-7rVLpFqKWqeVVVnf5-88vqHOKD-TnGeYmHbQw@mail.gmail.com \
--to=xli399@ucr.edu \
--cc=j.granados@samsung.com \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).