From: syzbot <syzbot+799d4cf78a7476483ba2@syzkaller.appspotmail.com>
To: brauner@kernel.org, cem@kernel.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [xfs?] general protection fault in do_move_mount (3)
Date: Wed, 14 May 2025 12:49:02 -0700 [thread overview]
Message-ID: <6824f3ae.a70a0220.3e9d8.001b.GAE@google.com> (raw)
In-Reply-To: <20250514184652.GP2023217@ZenIV>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+799d4cf78a7476483ba2@syzkaller.appspotmail.com
Tested-by: syzbot+799d4cf78a7476483ba2@syzkaller.appspotmail.com
Tested on:
commit: cfaefc95 fix a braino in "do_move_mount(): don't leak ..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
console output: https://syzkaller.appspot.com/x/log.txt?x=11865cd4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b9683d529ec1b880
dashboard link: https://syzkaller.appspot.com/bug?extid=799d4cf78a7476483ba2
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-05-14 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 17:39 [syzbot] [xfs?] general protection fault in do_move_mount (3) syzbot
2025-05-14 18:05 ` Al Viro
2025-05-14 18:13 ` syzbot
2025-05-14 18:21 ` Al Viro
2025-05-14 18:34 ` syzbot
2025-05-14 18:46 ` Al Viro
2025-05-14 19:49 ` syzbot [this message]
2025-07-13 5:16 ` [syzbot] [fs?] " 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=6824f3ae.a70a0220.3e9d8.001b.GAE@google.com \
--to=syzbot+799d4cf78a7476483ba2@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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.