From: syzbot <syzbot+1902c359bfcaf39c46f2@syzkaller.appspotmail.com>
To: ardb@kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, nogikh@google.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [efi] BUG: corrupted list in efivar_entry_remove
Date: Fri, 08 Dec 2023 08:25:04 -0800 [thread overview]
Message-ID: <000000000000d91934060c020627@google.com> (raw)
In-Reply-To: <CANp29Y4bxQzV-=rSQOBPfi2Rxrob_GTHZrsGAgvemvnXgC5a3g@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+1902c359bfcaf39c46f2@syzkaller.appspotmail.com
Tested on:
commit: ecbfc830 efivarfs: Move efivarfs list into superblock ..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git efivarfs-list-corruption-fix
console output: https://syzkaller.appspot.com/x/log.txt?x=147a4fcae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f62dd67b72f86455
dashboard link: https://syzkaller.appspot.com/bug?extid=1902c359bfcaf39c46f2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2023-12-08 16:25 UTC|newest]
Thread overview: 11+ 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 [this message]
2023-12-08 15:38 ` Ard Biesheuvel
2023-12-08 15:38 ` syzbot
2023-12-11 10:22 ` Ard Biesheuvel
2023-12-11 12:04 ` [syzbot] [efi] " 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=000000000000d91934060c020627@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 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.