All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e4470cc28308f2081ec8@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?] general protection fault in __umount_mnt
Date: Tue, 24 Mar 2026 02:08:03 -0700	[thread overview]
Message-ID: <69c25473.a70a0220.3cae05.000a.GAE@google.com> (raw)
In-Reply-To: <20260324-grauhaarig-gedeutet-f7cb2f86e1a6@brauner>

Hello,

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

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

Tested on:

commit:         14594a14 mount: always duplicate mount
git tree:       https://github.com/brauner/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17e5aa06580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d485346661badf84
dashboard link: https://syzkaller.appspot.com/bug?extid=e4470cc28308f2081ec8
compiler:       Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2026-03-24  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 22:45 [syzbot] [fs?] general protection fault in __umount_mnt syzbot
2026-03-23 15:17 ` Christian Brauner
2026-03-23 15:19   ` syzbot
2026-03-24  8:44   ` Christian Brauner
2026-03-24  9:08     ` syzbot [this message]
2026-03-28 13:16 ` syzbot
2026-03-28 21:09   ` Hillf Danton
2026-03-28 21:41     ` 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=69c25473.a70a0220.3cae05.000a.GAE@google.com \
    --to=syzbot+e4470cc28308f2081ec8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.