public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kees Cook <keescook@chromium.org>
Cc: davem@davemloft.net, lkp@intel.com, kuba@kernel.org,
	pabeni@redhat.com, yajun.deng@linux.dev,
	zhengyongjun3@huawei.com, morbo@google.com,
	linux-decnet-user@lists.sourceforge.net, netdev@vger.kernel.org,
	nathan@kernel.org, ndesaulniers@google.com, trix@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] decnet: Use container_of() for struct dn_neigh casts
Date: Tue, 10 May 2022 10:40:12 +0000	[thread overview]
Message-ID: <165217921289.11394.178390152550838154.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220508102217.2647184-1-keescook@chromium.org>

Hello:

This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Sun,  8 May 2022 03:22:17 -0700 you wrote:
> Clang's structure layout randomization feature gets upset when it sees
> struct neighbor (which is randomized) cast to struct dn_neigh:
> 
> net/decnet/dn_route.c:1123:15: error: casting from randomized structure pointer type 'struct neighbour *' to 'struct dn_neigh *'
> 			gateway = ((struct dn_neigh *)neigh)->addr;
> 				   ^
> 
> [...]

Here is the summary with links:
  - decnet: Use container_of() for struct dn_neigh casts
    https://git.kernel.org/netdev/net/c/dc5306a8c0ea

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



      reply	other threads:[~2022-05-10 10:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 10:22 [PATCH] decnet: Use container_of() for struct dn_neigh casts Kees Cook
2022-05-10 10:40 ` 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=165217921289.11394.178390152550838154.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-decnet-user@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=trix@redhat.com \
    --cc=yajun.deng@linux.dev \
    --cc=zhengyongjun3@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox