From: patchwork-bot+netdevbpf@kernel.org
To: Claudiu Manoil <claudiu.manoil@nxp.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net] enetc: Fix illegal access when reading affinity_hint
Date: Sun, 19 Sep 2021 11:20:09 +0000 [thread overview]
Message-ID: <163205040906.14261.2098100374293719653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210917102206.20616-1-claudiu.manoil@nxp.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Fri, 17 Sep 2021 13:22:05 +0300 you wrote:
> irq_set_affinity_hit() stores a reference to the cpumask_t
> parameter in the irq descriptor, and that reference can be
> accessed later from irq_affinity_hint_proc_show(). Since
> the cpu_mask parameter passed to irq_set_affinity_hit() has
> only temporary storage (it's on the stack memory), later
> accesses to it are illegal. Thus reads from the corresponding
> procfs affinity_hint file can result in paging request oops.
>
> [...]
Here is the summary with links:
- [net] enetc: Fix illegal access when reading affinity_hint
https://git.kernel.org/netdev/net/c/7237a494decf
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-09-19 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 10:22 [PATCH net] enetc: Fix illegal access when reading affinity_hint Claudiu Manoil
2021-09-17 10:22 ` [PATCH net] enetc: Fix uninitialized struct dim_sample field usage Claudiu Manoil
2021-09-19 11:20 ` patchwork-bot+netdevbpf
2021-09-19 11: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=163205040906.14261.2098100374293719653.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 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).