From: syzbot <syzbot+5b64180f8d9e39d3f061@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fuse?] KASAN: slab-use-after-free Read in fuse_test_super
Date: Mon, 28 Aug 2023 04:21:29 -0700 [thread overview]
Message-ID: <0000000000005160910603f9e56f@google.com> (raw)
In-Reply-To: <20230828103619.3855-1-hdanton@sina.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git on commit 28c736b0e92e: failed to run ["git" "fetch" "--force" "--tags" "fc608f7504e8b3e110eb6e7b798cef357818c5e1"]: exit status 1
error: cannot lock ref 'refs/tags/v6.5': 'refs/tags/v6.5/vfs.fixes' exists; cannot create 'refs/tags/v6.5'
From https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
! [new tag] v6.5 -> v6.5 (unable to update local ref)
error: some local refs could not be updated; try running
'git remote prune fc608f7504e8b3e110eb6e7b798cef357818c5e1' to remove any old, conflicting branches
Tested on:
commit: [unknown
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 28c736b0e92e
kernel config: https://syzkaller.appspot.com/x/.config?x=20999f779fa96017
dashboard link: https://syzkaller.appspot.com/bug?extid=5b64180f8d9e39d3f061
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=13359beba80000
next parent reply other threads:[~2023-08-28 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230828103619.3855-1-hdanton@sina.com>
2023-08-28 11:21 ` syzbot [this message]
[not found] <20230828115734.3980-1-hdanton@sina.com>
2023-08-28 12:32 ` [syzbot] [fuse?] KASAN: slab-use-after-free Read in fuse_test_super syzbot
2023-08-26 23:40 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=0000000000005160910603f9e56f@google.com \
--to=syzbot+5b64180f8d9e39d3f061@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--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.