From: patchwork-bot+netdevbpf@kernel.org
To: Miko Larsson <mikoxyzzz@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
jiri@resnulli.us, pabeni@redhat.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH] net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path
Date: Mon, 13 Feb 2023 09:50:16 +0000 [thread overview]
Message-ID: <167628181697.13846.4024635767323852589.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <2f74aab82a40e4c11c91ccba40f5b620f6cb209c.camel@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 10 Feb 2023 09:13:44 +0100 you wrote:
> syzbot reported that act_len in kalmia_send_init_packet() is
> uninitialized when passing it to the first usb_bulk_msg error path. Jiri
> Pirko noted that it's pointless to pass it in the error path, and that
> the value that would be printed in the second error path would be the
> value of act_len from the first call to usb_bulk_msg.[1]
>
> With this in mind, let's just not pass act_len to the usb_bulk_msg error
> paths.
>
> [...]
Here is the summary with links:
- net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path
https://git.kernel.org/netdev/net/c/c68f345b7c42
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-02-13 9:50 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
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 [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=167628181697.13846.4024635767323852589.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mikoxyzzz@gmail.com \
--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