From: patchwork-bot+netdevbpf@kernel.org
To: Roberto Sassu <roberto.sassu@huaweicloud.com>
Cc: andrii@kernel.org, mykolal@fb.com, ast@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, song@kernel.org,
yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org,
shuah@kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org, mattbobrowski@google.com,
zohar@linux.ibm.com, roberto.sassu@huawei.com
Subject: Re: [PATCH] bpf: Fix IMA test
Date: Wed, 08 Mar 2023 19:20:18 +0000 [thread overview]
Message-ID: <167830321841.2736.12501173221675335509.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230308103713.1681200-1-roberto.sassu@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 8 Mar 2023 11:37:13 +0100 you wrote:
> From: Roberto Sassu <roberto.sassu@huawei.com>
>
> Commit 62622dab0a28 ("ima: return IMA digest value only when IMA_COLLECTED
> flag is set") caused bpf_ima_inode_hash() to refuse to give non-fresh
> digests. IMA test #3 assumed the old behavior, that bpf_ima_inode_hash()
> still returned also non-fresh digests.
>
> [...]
Here is the summary with links:
- bpf: Fix IMA test
https://git.kernel.org/bpf/bpf-next/c/12fabae03ca6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-08 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 10:37 [PATCH] bpf: Fix IMA test Roberto Sassu
2023-03-08 10:40 ` Roberto Sassu
2023-03-08 19:17 ` Andrii Nakryiko
2023-03-08 11:03 ` Matt Bobrowski
2023-03-08 12:05 ` Roberto Sassu
2023-03-08 12:24 ` Matt Bobrowski
2023-03-08 19:20 ` 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=167830321841.2736.12501173221675335509.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mattbobrowski@google.com \
--cc=mykolal@fb.com \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.com \
--cc=zohar@linux.ibm.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