From: syzbot <syzbot+0b2e79f91ff6579bfa5b@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] WARNING in nsproxy_ns_active_put
Date: Fri, 07 Nov 2025 03:50:06 -0800 [thread overview]
Message-ID: <690ddcee.a70a0220.22f260.0047.GAE@google.com> (raw)
In-Reply-To: <20251107111638.19373-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in alloc_pid
------------[ cut here ]------------
WARNING: ./include/linux/ns_common.h:288 at __ns_ref_active_get include/linux/ns_common.h:288 [inline], CPU#1: syz-executor/6382
WARNING: ./include/linux/ns_common.h:288 at alloc_pid+0xad6/0xc70 kernel/pid.c:285, CPU#1: syz-executor/6382
Modules linked in:
CPU: 1 UID: 0 PID: 6382 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:__ns_ref_active_get include/linux/ns_common.h:288 [inline]
RIP: 0010:alloc_pid+0xad6/0xc70 kernel/pid.c:285
Code: cc e8 3e d8 34 00 be 02 00 00 00 eb 0a e8 32 d8 34 00 be 01 00 00 00 48 89 df e8 65 da 0c 03 e9 84 fa ff ff e8 1b d8 34 00 90 <0f> 0b 90 e9 2c fd ff ff e8 0d d8 34 00 90 0f 0b 90 e9 5b fd ff ff
RSP: 0018:ffffc9000213f9d8 EFLAGS: 00010293
RAX: ffffffff818cfa95 RBX: ffff888074ae5998 RCX: ffff88802a181e80
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: ffff888024e7a701 R08: ffff888074ae599b R09: 1ffff1100e95cb33
R10: dffffc0000000000 R11: ffffed100e95cb34 R12: dffffc0000000000
R13: 1ffff110049cf511 R14: ffff888074ae5830 R15: dffffc0000000000
FS: 000055558ad86500(0000) GS:ffff888125b79000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f201af156c0 CR3: 0000000078776000 CR4: 00000000003526f0
Call Trace:
<TASK>
copy_process+0x18e7/0x3930 kernel/fork.c:2196
kernel_clone+0x21e/0x840 kernel/fork.c:2609
__do_sys_clone kernel/fork.c:2750 [inline]
__se_sys_clone kernel/fork.c:2734 [inline]
__x64_sys_clone+0x18b/0x1e0 kernel/fork.c:2734
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f201a185e13
Code: 1f 84 00 00 00 00 00 64 48 8b 04 25 10 00 00 00 45 31 c0 31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 89 c2 85 c0 75 2c 64 48 8b 04 25 10 00 00
RSP: 002b:00007ffe79514908 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f201a185e13
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000001
R10: 000055558ad867d0 R11: 0000000000000246 R12: 0000000000000000
R13: 00000000000927c0 R14: 00000000000271be R15: 00007ffe79514aa0
</TASK>
Tested on:
commit: 9c0826a5 Add linux-next specific files for 20251107
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=11f67012580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4f8fcc6438a785e7
dashboard link: https://syzkaller.appspot.com/bug?extid=0b2e79f91ff6579bfa5b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1755ca92580000
next parent reply other threads:[~2025-11-07 11:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251107111638.19373-1-kartikey406@gmail.com>
2025-11-07 11:50 ` syzbot [this message]
[not found] <20251107114335.22409-1-kartikey406@gmail.com>
2025-11-07 13:44 ` [syzbot] [fs?] WARNING in nsproxy_ns_active_put syzbot
[not found] <20251107114102.22298-1-kartikey406@gmail.com>
2025-11-07 13:06 ` syzbot
[not found] <20251107101419.15312-1-kartikey406@gmail.com>
2025-11-07 10:42 ` syzbot
2025-11-06 1:36 syzbot
2025-11-09 8:24 ` syzbot
2025-11-11 9:24 ` Christian Brauner
2025-11-11 9:46 ` syzbot
2025-11-11 10:26 ` Christian Brauner
2025-11-11 11:02 ` syzbot
2025-11-11 11:23 ` Christian Brauner
2025-11-11 11:38 ` Christian Brauner
2025-11-11 13:03 ` syzbot
2025-11-11 15:07 ` Christian Brauner
2025-11-11 16:14 ` 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=690ddcee.a70a0220.22f260.0047.GAE@google.com \
--to=syzbot+0b2e79f91ff6579bfa5b@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.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