From: syzbot <syzbot+0a8655a80e189278487e@syzkaller.appspotmail.com>
To: brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] WARNING in nsproxy_ns_active_get
Date: Wed, 12 Nov 2025 02:18:05 -0800 [thread overview]
Message-ID: <69145edd.a70a0220.22f260.015b.GAE@google.com> (raw)
In-Reply-To: <20251112-ferien-trott-4d99d59d676d@brauner>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0a8655a80e189278487e@syzkaller.appspotmail.com
Tested-by: syzbot+0a8655a80e189278487e@syzkaller.appspotmail.com
Tested on:
commit: 53974b87 nsproxy: fix free_nsproxy() and simplify crea..
git tree: https://github.com/brauner/linux.git namespace-6.19
console output: https://syzkaller.appspot.com/x/log.txt?x=143dec12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=59952e73920025e4
dashboard link: https://syzkaller.appspot.com/bug?extid=0a8655a80e189278487e
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-11-12 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 1:35 [syzbot] [fs?] WARNING in nsproxy_ns_active_get syzbot
2025-11-07 11:44 ` Forwarded: [PATCH] nsfs: skip active reference management on initial namespaces syzbot
2025-11-11 12:04 ` [syzbot] [fs?] WARNING in nsproxy_ns_active_get Christian Brauner
2025-11-11 13:54 ` syzbot
2025-11-12 9:44 ` Christian Brauner
2025-11-12 10:18 ` syzbot [this message]
[not found] <20251107114435.22442-1-kartikey406@gmail.com>
2025-11-07 14:16 ` 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=69145edd.a70a0220.22f260.015b.GAE@google.com \
--to=syzbot+0a8655a80e189278487e@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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