From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+1957b26299cf3ff7890c@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] WARNING in destroy_super_work
Date: Fri, 7 Nov 2025 16:54:21 +0800 [thread overview]
Message-ID: <20251107085422.8964-1-hdanton@sina.com> (raw)
In-Reply-To: <690da04f.a70a0220.22f260.0027.GAE@google.com>
> Date: Thu, 06 Nov 2025 23:31:27 -0800
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 982312090977 Add linux-next specific files for 20251103
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=17b2932f980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=43cc0e31558cb527
> dashboard link: https://syzkaller.appspot.com/bug?extid=1957b26299cf3ff7890c
> compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1347817c580000
#syz test
--- x/kernel/nscommon.c
+++ y/kernel/nscommon.c
@@ -117,9 +117,7 @@ struct ns_common *__must_check ns_owner(
void __ns_ref_active_get_owner(struct ns_common *ns)
{
- ns = ns_owner(ns);
- if (ns)
- WARN_ON_ONCE(atomic_add_negative(1, &ns->__ns_ref_active));
+ __ns_ref_active_resurrect(ns);
}
/*
--
next prev parent reply other threads:[~2025-11-07 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 7:31 [syzbot] [fs?] WARNING in destroy_super_work syzbot
2025-11-07 8:54 ` Hillf Danton [this message]
2025-11-07 10:10 ` syzbot
2025-11-07 22:49 ` Forwarded: " syzbot
2025-11-09 13:39 ` Christian Brauner
2025-11-09 14:11 ` syzbot
[not found] <20251107-rackern-unbegreiflich-e49525c53d66@brauner>
2025-11-07 23:59 ` 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=20251107085422.8964-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+1957b26299cf3ff7890c@syzkaller.appspotmail.com \
--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