All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+1902c359bfcaf39c46f2@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: corrupted list in efivar_entry_remove
Date: Fri, 26 Aug 2022 19:41:11 -0700	[thread overview]
Message-ID: <000000000000aa392d05e72ff61e@google.com> (raw)
In-Reply-To: <20220827023941.2613-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/torvalds/linux.git on commit 680fb5b009e8: failed to run ["git" "checkout" "680fb5b009e8"]: exit status 1
error: pathspec '680fb5b009e8' did not match any file(s) known to git



Tested on:

commit:         [unknown 
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 680fb5b009e8
dashboard link: https://syzkaller.appspot.com/bug?extid=1902c359bfcaf39c46f2
compiler:       
userspace arch: arm64
patch:          https://syzkaller.appspot.com/x/patch.diff?x=15835ae7080000


       reply	other threads:[~2022-08-27  2:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220827023941.2613-1-hdanton@sina.com>
2022-08-27  2:41 ` syzbot [this message]
     [not found] <20220827034201.2669-1-hdanton@sina.com>
2022-08-27  3:43 ` [syzbot] BUG: corrupted list in efivar_entry_remove syzbot
2022-08-26 11:10 syzbot
2023-12-08 15:24 ` Ard Biesheuvel
2023-12-08 15:24   ` syzbot
2023-12-08 15:38     ` Aleksandr Nogikh
2023-12-08 15:40       ` Ard Biesheuvel
2023-12-08 15:40         ` syzbot
2023-12-08 15:38 ` Ard Biesheuvel
2023-12-08 15:38   ` syzbot
2023-12-11 10:22 ` Ard Biesheuvel

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=000000000000aa392d05e72ff61e@google.com \
    --to=syzbot+1902c359bfcaf39c46f2@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.