From: syzbot <syzbot+1902c359bfcaf39c46f2@syzkaller.appspotmail.com>
To: ardb@kernel.org
Cc: ardb@kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: corrupted list in efivar_entry_remove
Date: Fri, 08 Dec 2023 07:38:38 -0800 [thread overview]
Message-ID: <000000000000c2015d060c016027@google.com> (raw)
In-Reply-To: <CAMj1kXFBa2z3FKaEzRyJ1ugZy7P3VfS18hheDs8-+pZ+Gch4pQ@mail.gmail.com>
> On Fri, 26 Aug 2022 at 13:10, syzbot
> <syzbot+1902c359bfcaf39c46f2@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following issue on:
>>
>> HEAD commit: 680fb5b009e8 Merge tag 'arm64-upstream' into for-kernelci
>> git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
>> console output: https://syzkaller.appspot.com/x/log.txt?x=126f0865080000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=4557ad2600fc45f4
>> dashboard link: https://syzkaller.appspot.com/bug?extid=1902c359bfcaf39c46f2
>> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
>> userspace arch: arm64
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10039fc3080000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f4ebc3080000
>>
>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>> Reported-by: syzbot+1902c359bfcaf39c46f2@syzkaller.appspotmail.com
>>
>
> #syz test git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git
want either no args or 2 args (repo, branch), got 1
> ecbfc830fd039
next prev parent reply other threads:[~2023-12-08 15:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 11:10 [syzbot] BUG: corrupted list in efivar_entry_remove 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 16:25 ` [syzbot] [efi] " syzbot
2023-12-08 15:38 ` [syzbot] " Ard Biesheuvel
2023-12-08 15:38 ` syzbot [this message]
2023-12-11 10:22 ` Ard Biesheuvel
2023-12-11 12:04 ` [syzbot] [efi] " syzbot
[not found] <20220827023941.2613-1-hdanton@sina.com>
2022-08-27 2:41 ` [syzbot] " syzbot
[not found] <20220827034201.2669-1-hdanton@sina.com>
2022-08-27 3:43 ` 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=000000000000c2015d060c016027@google.com \
--to=syzbot+1902c359bfcaf39c46f2@syzkaller.appspotmail.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox