From: syzbot <syzbot+6efc50cc1f8d718d6cb7@syzkaller.appspotmail.com>
To: davem@davemloft.net, dhowells@redhat.com,
herbert@gondor.apana.org.au, kuba@kernel.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] KASAN: slab-out-of-bounds Read in extract_iter_to_sg
Date: Thu, 15 Jun 2023 09:29:32 -0700 [thread overview]
Message-ID: <000000000000bc6a1705fe2d92c1@google.com> (raw)
In-Reply-To: <256755.1686844894@warthog.procyon.org.uk>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+6efc50cc1f8d718d6cb7@syzkaller.appspotmail.com
Tested on:
commit: 97c5209b leds: trigger: netdev: uninitialized variable..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git main
console output: https://syzkaller.appspot.com/x/log.txt?x=1258baf7280000
kernel config: https://syzkaller.appspot.com/x/.config?x=526f919910d4a671
dashboard link: https://syzkaller.appspot.com/bug?extid=6efc50cc1f8d718d6cb7
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=12c65e17280000
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2023-06-15 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 9:40 [syzbot] [crypto?] KASAN: slab-out-of-bounds Read in extract_iter_to_sg syzbot
2023-06-14 15:51 ` David Howells
2023-06-14 23:17 ` syzbot
2023-06-15 14:21 ` David Howells
2023-06-15 20:24 ` David Howells
2023-06-15 20:24 ` David Howells
2023-06-15 21:02 ` syzbot
2023-06-15 12:07 ` David Howells
2023-06-15 15:06 ` syzbot
2023-06-15 16:01 ` David Howells
2023-06-15 16:29 ` syzbot [this message]
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=000000000000bc6a1705fe2d92c1@google.com \
--to=syzbot+6efc50cc1f8d718d6cb7@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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.