From: Miko Larsson <mikoxyzzz@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [UNTESTED PATCH] net/usb: kalmia: Fix uninit-value in kalmia_send_init_packet
Date: Tue, 31 Jan 2023 12:48:54 +0100 [thread overview]
Message-ID: <a9d5c49536b3dc5039d981952aa60db6266516e2.camel@gmail.com> (raw)
In-Reply-To: <Y9j9jAHLDBsTxZB7@kroah.com>
On Tue, 2023-01-31 at 12:37 +0100, Greg KH wrote:
> On Tue, Jan 31, 2023 at 12:14:54PM +0100, Miko Larsson wrote:
> > > From ef617d8df22945b871ab989e25c07d7c60ae21f6 Mon Sep 17 00:00:00
> > > 2001
> > From: Miko Larsson <mikoxyzzz@gmail.com>
> > Date: Tue, 31 Jan 2023 11:01:20 +0100
>
> Why is this in the changelog text?
D'oh, sorry about that. Imported the patch directly into Evolution
without trimming that away.
> > Subject: [UNTESTED PATCH] net/usb: kalmia: Fix uninit-value in
> > kalmia_send_init_packet
> >
> > syzbot reports that act_len in kalmia_send_init_packet() is
> > uninitialized. Attempt to fix this by initializing it to 0.
>
> You can send patches to syzbot to have it test things, have you tried
> that?
Didn't know that, will try!
--
~miko
next prev parent reply other threads:[~2023-01-31 11:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 11:14 [UNTESTED PATCH] net/usb: kalmia: Fix uninit-value in kalmia_send_init_packet Miko Larsson
2023-01-31 11:37 ` Greg KH
2023-01-31 11:48 ` Miko Larsson [this message]
2023-01-31 14:20 ` [PATCH v2] " Miko Larsson
2023-01-31 14:56 ` Greg KH
2023-02-01 12:19 ` Jiri Pirko
2023-02-09 14:47 ` Miko Larsson
2023-02-09 15:12 ` Jiri Pirko
2023-02-10 8:13 ` [PATCH] net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path Miko Larsson
2023-02-10 16:08 ` Alexander H Duyck
2023-02-13 9:50 ` patchwork-bot+netdevbpf
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=a9d5c49536b3dc5039d981952aa60db6266516e2.camel@gmail.com \
--to=mikoxyzzz@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).