BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: ndesaulniers@google.com, andrii@kernel.org, nathan@kernel.org,
	 daniel@iogearbox.net, ast@kernel.org,
	steffen.klassert@secunet.com,  antony.antony@secunet.com,
	alexei.starovoitov@gmail.com, yonghong.song@linux.dev,
	 martin.lau@linux.dev, song@kernel.org, john.fastabend@gmail.com,
	 kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
	jolsa@kernel.org,  trix@redhat.com, bpf@vger.kernel.org,
	linux-kernel@vger.kernel.org,  llvm@lists.linux.dev,
	devel@linux-ipsec.org, netdev@vger.kernel.org
Subject: Re: [PATCH ipsec-next v2 3/6] libbpf: Add BPF_CORE_WRITE_BITFIELD() macro
Date: Fri, 01 Dec 2023 18:13:22 +0200	[thread overview]
Message-ID: <18808a1815e76a3c3fb661ff6a588a50389b1475.camel@gmail.com> (raw)
In-Reply-To: <ib27gbqj6c6ilblugm5kalwyfty6h4zujhvykw4a562uorqzjn@6wxeino6q7vk>

On Thu, 2023-11-30 at 18:33 -0700, Daniel Xu wrote:
[...]
> Good call about adding tests -- I found a few bugs with the code from
> the other thread. But boy did they take a lot of brain cells to figure
> out.
> 
> There was some 6th grade algebra involved too -- I'll do my best to
> explain it in the commit msg for v3.
> 
> Here are the fixes in case you are curious:

Ouch, I knew my code from 3am can't be trusted, sorry for that.
Your math seem to make sense, thank you.

[...]

  reply	other threads:[~2023-12-01 16:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 17:54 [PATCH ipsec-next v2 0/6] Add bpf_xdp_get_xfrm_state() kfunc Daniel Xu
2023-11-28 17:54 ` [PATCH ipsec-next v2 1/6] bpf: xfrm: " Daniel Xu
2023-11-28 17:54 ` [PATCH ipsec-next v2 2/6] bpf: xfrm: Add bpf_xdp_xfrm_state_release() kfunc Daniel Xu
2023-11-28 17:54 ` [PATCH ipsec-next v2 3/6] libbpf: Add BPF_CORE_WRITE_BITFIELD() macro Daniel Xu
2023-11-28 17:59   ` Eduard Zingerman
2023-11-28 19:15     ` Daniel Xu
2023-12-01  1:33     ` Daniel Xu
2023-12-01 16:13       ` Eduard Zingerman [this message]
2023-12-01 19:11       ` Andrii Nakryiko
2023-12-01 19:13         ` Andrii Nakryiko
2023-12-01 20:05           ` Daniel Xu
2023-11-28 17:54 ` [PATCH ipsec-next v2 4/6] bpf: selftests: test_tunnel: Use vmlinux.h declarations Daniel Xu
2023-11-28 17:54 ` [PATCH ipsec-next v2 5/6] bpf: selftests: Move xfrm tunnel test to test_progs Daniel Xu
2023-11-28 17:54 ` [PATCH ipsec-next v2 6/6] bpf: xfrm: Add selftest for bpf_xdp_get_xfrm_state() Daniel Xu

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=18808a1815e76a3c3fb661ff6a588a50389b1475.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=antony.antony@secunet.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=devel@linux-ipsec.org \
    --cc=dxu@dxuuu.xyz \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=trix@redhat.com \
    --cc=yonghong.song@linux.dev \
    /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