From: patchwork-bot+netdevbpf@kernel.org
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: sgoutham@marvell.com, hkalra@marvell.com, lcherian@marvell.com,
gakula@marvell.com, jerinj@marvell.com, hkelam@marvell.com,
sbhatta@marvell.com, davem@davemloft.net, kuba@kernel.org,
bbudiredla@marvell.com, rsaladi2@marvell.com,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net] octeontx2-af: debugfs: don't corrupt user memory
Date: Thu, 18 Nov 2021 04:30:09 +0000 [thread overview]
Message-ID: <163720980903.29413.8714907245021841032.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211117073454.GD5237@kili>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 17 Nov 2021 10:34:54 +0300 you wrote:
> The user supplies the "count" value to say how big its read buffer is.
> The rvu_dbg_lmtst_map_table_display() function does not take the "count"
> into account but instead just copies the whole table, potentially
> corrupting the user's data.
>
> Introduce the "ret" variable to store how many bytes we can copy. Also
> I changed the type of "off" to size_t to make using min() simpler.
>
> [...]
Here is the summary with links:
- [net] octeontx2-af: debugfs: don't corrupt user memory
https://git.kernel.org/netdev/net/c/a280ef90af01
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:[~2021-11-18 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 7:34 [PATCH net] octeontx2-af: debugfs: don't corrupt user memory Dan Carpenter
2021-11-18 4:30 ` 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=163720980903.29413.8714907245021841032.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bbudiredla@marvell.com \
--cc=dan.carpenter@oracle.com \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkalra@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=rsaladi2@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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.