bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Lau <kafai@fb.com>
To: Andrii Nakryiko <andriin@fb.com>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Alexei Starovoitov <ast@fb.com>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>
Subject: Re: [Potential Spoof] [PATCH bpf-next] bpf: fix cast to pointer from integer of different size warning
Date: Fri, 11 Oct 2019 05:15:11 +0000	[thread overview]
Message-ID: <20191011051507.akhuheqjizpfq7xx@kafai-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20191011042925.731290-1-andriin@fb.com>

On Thu, Oct 10, 2019 at 09:29:25PM -0700, Andrii Nakryiko wrote:
> Fix "warning: cast to pointer from integer of different size" when
> casting u64 addr to void *.
> Reported-by: kbuild test robot <lkp@intel.com>
> Signed-off-by: Andrii Nakryiko <andriin@fb.com>
Fixes: a23740ec43ba ("bpf: Track contents of read-only maps as scalars")

Acked-by: Martin KaFai Lau <kafai@fb.com>

  reply	other threads:[~2019-10-11  5:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  4:29 [PATCH bpf-next] bpf: fix cast to pointer from integer of different size warning Andrii Nakryiko
2019-10-11  5:15 ` Martin Lau [this message]
2019-10-11 17:18   ` [Potential Spoof] " Andrii Nakryiko

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191011051507.akhuheqjizpfq7xx@kafai-mbp.dhcp.thefacebook.com \
    --to=kafai@fb.com \
    --cc=andriin@fb.com \
    --cc=ast@fb.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \


* 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).