BPF List
 help / color / mirror / Atom feed
From: Andrei Matei <andreimatei1@gmail.com>
To: bpf@vger.kernel.org
Cc: sunhao.th@gmail.com, andrii.nakryiko@gmail.com,
	eddyz87@gmail.com, Andrei Matei <andreimatei1@gmail.com>
Subject: [PATCH bpf-next v5 0/3] bpf: fix verification of indirect var-off stack access
Date: Wed,  6 Dec 2023 23:11:47 -0500	[thread overview]
Message-ID: <20231207041150.229139-1-andreimatei1@gmail.com> (raw)

V4 to V5:
  - split the test into a separate patch

V3 to V4:
  - include a test per Eduard's request
  - target bpf-next per Alexei's request (patches didn't change)


V2 to V3:
  - simplify checks for max_off (don't call
    check_stack_slot_within_bounds for it)
  - append a commit to protect against overflow in the addition of the
    register and the offset

V1 to V2:
  - fix max_off calculation for access size = 0


Andrei Matei (3):
  bpf: fix verification of indirect var-off stack access
  bpf: add verifier regression test for previous patch
  bpf: guard stack limits against 32bit overflow

 kernel/bpf/verifier.c                         | 20 +++++--------
 .../selftests/bpf/progs/verifier_var_off.c    | 29 +++++++++++++++++++
 2 files changed, 36 insertions(+), 13 deletions(-)

-- 
2.40.1


             reply	other threads:[~2023-12-07  4:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07  4:11 Andrei Matei [this message]
2023-12-07  4:11 ` [PATCH bpf-next v5 1/3] bpf: fix verification of indirect var-off stack access Andrei Matei
2023-12-07  4:11 ` [PATCH bpf-next v5 2/3] bpf: add verifier regression test for previous patch Andrei Matei
2023-12-07  4:11 ` [PATCH bpf-next v5 3/3] bpf: guard stack limits against 32bit overflow Andrei Matei
2023-12-07 19:10 ` [PATCH bpf-next v5 0/3] bpf: fix verification of indirect var-off stack access patchwork-bot+netdevbpf

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=20231207041150.229139-1-andreimatei1@gmail.com \
    --to=andreimatei1@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=sunhao.th@gmail.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