All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jerry Ray <jerry.ray@microchip.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH] micrel: ksz8851: fixes struct pointer issue
Date: Wed, 24 Aug 2022 12:10:17 +0000	[thread overview]
Message-ID: <166134301711.8334.15216665637776829191.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220822213932.12848-1-jerry.ray@microchip.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 22 Aug 2022 16:39:32 -0500 you wrote:
> Issue found during code review. This bug has no impact as long as the
> ks8851_net structure is the first element of the ks8851_net_spi structure.
> As long as the offset to the ks8851_net struct is zero, the container_of()
> macro is subtracting 0 and therefore no damage done. But if the
> ks8851_net_spi struct is ever modified such that the ks8851_net struct
> within it is no longer the first element of the struct, then the bug would
> manifest itself and cause problems.
> 
> [...]

Here is the summary with links:
  - micrel: ksz8851: fixes struct pointer issue
    https://git.kernel.org/netdev/net-next/c/fef5de753ff0

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



      reply	other threads:[~2022-08-24 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 21:39 [PATCH] micrel: ksz8851: fixes struct pointer issue Jerry Ray
2022-08-24 12:10 ` 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=166134301711.8334.15216665637776829191.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --cc=jerry.ray@microchip.com \
    --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 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.