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, nogikh@google.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: corrupted list in efivar_entry_remove
Date: Fri, 08 Dec 2023 07:40:18 -0800 [thread overview]
Message-ID: <000000000000bc9918060c0166e7@google.com> (raw)
In-Reply-To: <CAMj1kXGdLTsDnvqb3pe--eW3p480kbDRfyydMCUOW1m-3Bf9cg@mail.gmail.com>
> On Fri, 8 Dec 2023 at 16:38, Aleksandr Nogikh <nogikh@google.com> wrote:
>>
>> If a command spans over two lines, syzbot expects a colon.
>>
>> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git
>> efivarfs-list-corruption-fix
>>
>
> It is Gmail that is breaking the line here
>
>
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git:
"git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git:" does not look like a valid git repo address.
> efivarfs-list-corruption-fix
next prev parent reply other threads:[~2023-12-08 15:40 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 [this message]
2023-12-08 16:25 ` [syzbot] [efi] " syzbot
2023-12-08 15:38 ` [syzbot] " Ard Biesheuvel
2023-12-08 15:38 ` syzbot
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=000000000000bc9918060c0166e7@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=nogikh@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox