All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yevhen Orlov <yevhen.orlov@plvision.eu>
Cc: netdev@vger.kernel.org, volodymyr.mytnyk@plvision.eu,
	taras.chornyi@plvision.eu, mickeyr@marvell.com,
	serhiy.pshyk@plvision.eu, tchornyi@marvell.com,
	davem@davemloft.net, kuba@kernel.org, vkochan@marvell.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: marvell: prestera: fix incorrect structure access
Date: Sat, 18 Dec 2021 03:30:14 +0000	[thread overview]
Message-ID: <163979821472.17814.11509702990078452116.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211216171714.11341-1-yevhen.orlov@plvision.eu>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 16 Dec 2021 19:17:14 +0200 you wrote:
> In line:
> 	upper = info->upper_dev;
> We access upper_dev field, which is related only for particular events
> (e.g. event == NETDEV_CHANGEUPPER). So, this line cause invalid memory
> access for another events,
> when ptr is not netdev_notifier_changeupper_info.
> 
> [...]

Here is the summary with links:
  - [net] net: marvell: prestera: fix incorrect structure access
    https://git.kernel.org/netdev/net/c/2efc2256febf

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-12-18  3:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 17:17 [PATCH net] net: marvell: prestera: fix incorrect structure access Yevhen Orlov
2021-12-18  3: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=163979821472.17814.11509702990078452116.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mickeyr@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=serhiy.pshyk@plvision.eu \
    --cc=taras.chornyi@plvision.eu \
    --cc=tchornyi@marvell.com \
    --cc=vkochan@marvell.com \
    --cc=volodymyr.mytnyk@plvision.eu \
    --cc=yevhen.orlov@plvision.eu \
    /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.