public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+55fd613012e606d75d45@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?] possible deadlock in put_mnt_ns
Date: Fri, 16 Jan 2026 05:44:02 -0800	[thread overview]
Message-ID: <696a40a2.050a0220.58bed.004d.GAE@google.com> (raw)
In-Reply-To: <20260116-kostbar-blass-171a72be1845@brauner>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+55fd613012e606d75d45@syzkaller.appspotmail.com
Tested-by: syzbot+55fd613012e606d75d45@syzkaller.appspotmail.com

Tested on:

commit:         e64f65a7 FOLDME
git tree:       https://github.com/brauner/linux.git vfs-7.0.namespace
console output: https://syzkaller.appspot.com/x/log.txt?x=15fac39a580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=dac5329a4190a189
dashboard link: https://syzkaller.appspot.com/bug?extid=55fd613012e606d75d45
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.

      reply	other threads:[~2026-01-16 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15  9:50 [syzbot] [fs?] possible deadlock in put_mnt_ns syzbot
2026-01-16 10:40 ` Christian Brauner
2026-01-16 10:52   ` Christian Brauner
2026-01-16 13:44     ` syzbot [this message]

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=696a40a2.050a0220.58bed.004d.GAE@google.com \
    --to=syzbot+55fd613012e606d75d45@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