From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+799d4cf78a7476483ba2@syzkaller.appspotmail.com>
Cc: 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
Subject: Re: [syzbot] [xfs?] general protection fault in do_move_mount (3)
Date: Wed, 14 May 2025 19:46:52 +0100 [thread overview]
Message-ID: <20250514184652.GP2023217@ZenIV> (raw)
In-Reply-To: <20250514182111.GO2023217@ZenIV>
On Wed, May 14, 2025 at 07:21:11PM +0100, Al Viro wrote:
> On Wed, May 14, 2025 at 11:13:08AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot tried to test the proposed patch but the build/boot failed:
> >
> > failed to checkout kernel repo git://git.kernel.org//pub/scm/linux/kernel/git/viro/vfs.git/fixes: failed to run ["git" "fetch" "--force" "8a6d8037a5deb2a9d5184f299f9adb60b0c0ae04" "fixes"]: exit status 128
> > fatal: remote error: access denied or repository not exported: //pub/scm/linux/kernel/git/viro/vfs.git
>
> *blink*
>
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git 8a6d8037a5deb2a9d5184f299f9adb60b0c0ae04
>
> just in case the cut'n'paste damage (extra slash before 'pub') was not
> the only problem there...
... and that copied the bogus commit id from the error message. Sigh...
Anyway, actual commit id is cfaefc95bfa7eb92dd837ea9fb38bc84e62d79b5 and
curl 'https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git/patch/?id=cfaefc95bfa7eb92dd837ea9fb38bc84e62d79b5'
definitely finds it, so commit is there.
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git cfaefc95bfa7eb92dd837ea9fb38bc84e62d79b5
next prev parent reply other threads:[~2025-05-14 18:46 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 [this message]
2025-05-14 19:49 ` syzbot
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=20250514184652.GP2023217@ZenIV \
--to=viro@zeniv.linux.org.uk \
--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=syzbot+799d4cf78a7476483ba2@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 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.