From: patchwork-bot+netdevbpf@kernel.org
To: Hristo Venev <hristo@venev.name>
Cc: netdev@vger.kernel.org, ajit.khaparde@broadcom.com,
sriharsha.basavapatna@broadcom.com, somnath.kotur@broadcom.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mark.leonard@emulex.com,
sathya.perla@emulex.com, Suresh.Reddy@emulex.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] be2net: Fix buffer overflow in be_get_module_eeprom
Date: Tue, 19 Jul 2022 10:20:12 +0000 [thread overview]
Message-ID: <165822601287.18997.9680200835498152031.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220716085134.6095-1-hristo@venev.name>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 16 Jul 2022 11:51:34 +0300 you wrote:
> be_cmd_read_port_transceiver_data assumes that it is given a buffer that
> is at least PAGE_DATA_LEN long, or twice that if the module supports SFF
> 8472. However, this is not always the case.
>
> Fix this by passing the desired offset and length to
> be_cmd_read_port_transceiver_data so that we only copy the bytes once.
>
> [...]
Here is the summary with links:
- be2net: Fix buffer overflow in be_get_module_eeprom
https://git.kernel.org/netdev/net/c/d7241f679a59
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:[~2022-07-19 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 8:51 [PATCH] be2net: Fix buffer overflow in be_get_module_eeprom Hristo Venev
2022-07-19 10:20 ` 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=165822601287.18997.9680200835498152031.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Suresh.Reddy@emulex.com \
--cc=ajit.khaparde@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hristo@venev.name \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.leonard@emulex.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sathya.perla@emulex.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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