All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: bpf@vger.kernel.org, fsverity@lists.linux.dev,
	linux-kernel@vger.kernel.org, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
	memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
	yonghong.song@linux.dev, emil@etsalapatis.com, jolsa@kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH bpf v2 0/2] Fixes for bpf_get_fsverity_digest()
Date: Tue, 04 Aug 2026 07:30:10 +0000	[thread overview]
Message-ID: <178582861063.3014158.3566038608254697461.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260803181232.14743-1-ebiggers@kernel.org>

Hello:

This series was applied to bpf/bpf.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Mon,  3 Aug 2026 11:12:30 -0700 you wrote:
> Two fixes for bpf_get_fsverity_digest().
> 
> Changed in v2:
>     - Added patch to fix silent truncation.
>     - Updated commit message to clarify that the size > INT_MAX case
>       seems to be unreachable currently.
>     - Added Acked-bys
> 
> [...]

Here is the summary with links:
  - [bpf,v2,1/2] fsverity: Fix bpf_get_fsverity_digest() dynptr assumptions
    https://git.kernel.org/bpf/bpf/c/3e8ec7c03872
  - [bpf,v2,2/2] fsverity: Fix silent truncation in bpf_get_fsverity_digest()
    https://git.kernel.org/bpf/bpf/c/7c68ed5c5ad4

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



      parent reply	other threads:[~2026-08-04  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 18:12 [PATCH bpf v2 0/2] Fixes for bpf_get_fsverity_digest() Eric Biggers
2026-08-03 18:12 ` [PATCH bpf v2 1/2] fsverity: Fix bpf_get_fsverity_digest() dynptr assumptions Eric Biggers
2026-08-03 18:12 ` [PATCH bpf v2 2/2] fsverity: Fix silent truncation in bpf_get_fsverity_digest() Eric Biggers
2026-08-04  5:41   ` Song Liu
2026-08-04  7:30 ` 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=178582861063.3014158.3566038608254697461.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=ebiggers@kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=fsverity@lists.linux.dev \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=song@kernel.org \
    --cc=stable@vger.kernel.org \
    --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 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.