From: syzbot <syzbot+6641a61fe0e2e89ae8c5@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in xfrm_state_fini (3)
Date: Tue, 29 Jul 2025 02:05:02 -0700 [thread overview]
Message-ID: <68888ebe.a70a0220.13df61.0001.GAE@google.com> (raw)
In-Reply-To: <20250729081109.3381-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in xfrm_state_fini
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1084 at net/xfrm/xfrm_state.c:3293 xfrm_state_fini+0x270/0x2f0 net/xfrm/xfrm_state.c:3293
Modules linked in:
CPU: 1 UID: 0 PID: 1084 Comm: kworker/u8:6 Not tainted 6.16.0-syzkaller-g86aa72182095-dirty #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: netns cleanup_net
RIP: 0010:xfrm_state_fini+0x270/0x2f0 net/xfrm/xfrm_state.c:3293
Code: c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 18 dd 09 f8 48 8b 3b 5b 41 5c 41 5d 41 5e 41 5f 5d e9 06 ab ea f7 e8 31 c4 a7 f7 90 <0f> 0b 90 e9 fd fd ff ff e8 23 c4 a7 f7 90 0f 0b 90 e9 60 fe ff ff
RSP: 0018:ffffc90003a8f898 EFLAGS: 00010293
RAX: ffffffff8a17909f RBX: ffff888035c00000 RCX: ffff888026f79e00
RDX: 0000000000000000 RSI: ffffffff8db5f1fd RDI: ffff888026f79e00
RBP: ffffc90003a8f9b0 R08: ffffffff8f6025e7 R09: 1ffffffff1ec04bc
R10: dffffc0000000000 R11: fffffbfff1ec04bd R12: ffffffff8f600660
R13: 1ffff92000751f40 R14: ffff888035c014c0 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff888125d86000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efd65a94e9c CR3: 0000000031b09000 CR4: 0000000000350ef0
Call Trace:
<TASK>
xfrm_net_exit+0x2d/0x70 net/xfrm/xfrm_policy.c:4348
ops_exit_list net/core/net_namespace.c:200 [inline]
ops_undo_list+0x49a/0x990 net/core/net_namespace.c:253
cleanup_net+0x4c5/0x800 net/core/net_namespace.c:686
process_one_work kernel/workqueue.c:3238 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3321
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3402
kthread+0x711/0x8a0 kernel/kthread.c:464
ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Tested on:
commit: 86aa7218 Merge tag 'chrome-platform-v6.17' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=100531bc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6aef71a615d0cdf2
dashboard link: https://syzkaller.appspot.com/bug?extid=6641a61fe0e2e89ae8c5
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
patch: https://syzkaller.appspot.com/x/patch.diff?x=16798cf0580000
next prev parent reply other threads:[~2025-07-29 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 7:08 syzbot
2025-07-29 8:11 ` Hillf Danton
2025-07-29 9:05 ` syzbot [this message]
2025-07-29 11:01 ` Steffen Klassert
2025-07-29 11:09 ` Sabrina Dubroca
2025-07-29 18:47 ` syzbot
2025-08-28 11:06 ` Tetsuo Handa
2025-08-29 8:57 ` Sabrina Dubroca
2025-08-01 0:54 ` syzbot
[not found] <aIiYARi_eBdMAIhd@gauss3.secunet.de>
2025-07-29 9:44 ` syzbot
[not found] <aIiaPZa_jHAiuATa@gauss3.secunet.de>
2025-07-29 9:54 ` 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=68888ebe.a70a0220.13df61.0001.GAE@google.com \
--to=syzbot+6641a61fe0e2e89ae8c5@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 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®