mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, lis@redhat.com,
	syzkaller-bugs@googlegroups.com,  viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] general protection fault in do_move_mount (3)
Date: Sat, 12 Jul 2025 22:16:01 -0700	[thread overview]
Message-ID: <68734111.a70a0220.3b380f.0020.GAE@google.com> (raw)
In-Reply-To: <6824d556.a00a0220.104b28.0012.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 3b5260d12b1fe76b566fe182de8abc586b827ed0
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Fri May 23 23:20:36 2025 +0000

    Don't propagate mounts into detached trees

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=160a018c580000
start commit:   bec6f00f120e Merge tag 'usb-6.15-rc6' of git://git.kernel...
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=b9683d529ec1b880
dashboard link: https://syzkaller.appspot.com/bug?extid=799d4cf78a7476483ba2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17eb1670580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17794cf4580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: Don't propagate mounts into detached trees

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2025-07-13  5:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14 17:39 [syzbot] [xfs?] " 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
2025-07-13  5:16 ` 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=68734111.a70a0220.3b380f.0020.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=lis@redhat.com \
    --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
all inboxes | Powered by JetHome®