BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiang Wang <jiang.wang@bytedance.com>
Cc: bpf@vger.kernel.org, cong.wang@bytedance.com, kpsingh@google.com
Subject: Re: [PATCH] selftests/bpf: fix a compile error for BPF_F_BPRM_SECUREEXEC
Date: Tue, 29 Dec 2020 14:30:06 +0000	[thread overview]
Message-ID: <160925220648.7797.17187932953151501687.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201224011242.585967-1-jiang.wang@bytedance.com>

Hello:

This patch was applied to bpf/bpf.git (refs/heads/master):

On Thu, 24 Dec 2020 01:12:42 +0000 you wrote:
> When CONFIG_BPF_LSM is not configured, running bpf selftesting will show
> BPF_F_BPRM_SECUREEXEC undefined error for bprm_opts.c.
> 
> The problem is that bprm_opts.c includes vmliunx.h. The vmlinux.h is
> generated by "bpftool btf dump file ./vmlinux format c". On the other
> hand, BPF_F_BPRM_SECUREEXEC is defined in include/uapi/linux/bpf.h
> and used only in bpf_lsm.c. When CONFIG_BPF_LSM is not set, bpf_lsm
> will not be compiled, so vmlinux.h will not include definition of
> BPF_F_BPRM_SECUREEXEC.
> 
> [...]

Here is the summary with links:
  - selftests/bpf: fix a compile error for BPF_F_BPRM_SECUREEXEC
    https://git.kernel.org/bpf/bpf/c/da4282c17d69

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



      parent reply	other threads:[~2020-12-29 14:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  1:12 [PATCH] selftests/bpf: fix a compile error for BPF_F_BPRM_SECUREEXEC Jiang Wang
2020-12-28 18:37 ` Song Liu
2020-12-29  5:14   ` John Fastabend
2020-12-29 14:28     ` Daniel Borkmann
2020-12-29 18:39       ` [External] " Jiang Wang .
2020-12-28 18:41 ` Song Liu
2020-12-29 14: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=160925220648.7797.17187932953151501687.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=cong.wang@bytedance.com \
    --cc=jiang.wang@bytedance.com \
    --cc=kpsingh@google.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