From: patchwork-bot+linux-arm-msm@kernel.org
To: Jeffrey Hugo <jhugo@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3] bus: mhi: core: Sanity check values from remote device before use
Date: Wed, 26 May 2021 19:03:27 +0000 [thread overview]
Message-ID: <162205580736.26840.10114724449133441202.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1615411855-15053-1-git-send-email-jhugo@codeaurora.org>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Wed, 10 Mar 2021 14:30:55 -0700 you wrote:
> When parsing the structures in the shared memory, there are values which
> come from the remote device. For example, a transfer completion event
> will have a pointer to the tre in the relevant channel's transfer ring.
> As another example, event ring elements may specify a channel in which
> the event occurred, however the specified channel value may not be valid
> as no channel is defined at that index even though the index may be less
> than the maximum allowed index. Such values should be considered to be
> untrusted, and validated before use. If we blindly use such values, we
> may access invalid data or crash if the values are corrupted.
>
> [...]
Here is the summary with links:
- [v3] bus: mhi: core: Sanity check values from remote device before use
https://git.kernel.org/qcom/c/ec32332df764
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-05-26 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 21:30 [PATCH v3] bus: mhi: core: Sanity check values from remote device before use Jeffrey Hugo
2021-04-07 8:21 ` Manivannan Sadhasivam
2021-04-07 21:30 ` Hemant Kumar
2021-04-08 6:57 ` Manivannan Sadhasivam
2021-05-26 19:03 ` patchwork-bot+linux-arm-msm [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=162205580736.26840.10114724449133441202.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=jhugo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
/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.