public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Christian Brauner <brauner@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include: linux: Fix flex array member not at the end in bpf_empty_prog_array
Date: Thu, 3 Oct 2024 19:54:22 -0600	[thread overview]
Message-ID: <674d86d6-4073-4630-b8b1-fe73ab7e995e@embeddedor.com> (raw)
In-Reply-To: <20240930181700.22839-1-philipp.g.hortmann@gmail.com>



On 30/09/24 12:16, Philipp Hortmann wrote:
> Struct bpf_prog_array has a flex array member at the end and needs
> therefore to be last in struct bpf_empty_prog_array.
> 
> Signed-off-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>

Acked-by: Gustavo A. R. Silva <gustavoars@kernel.org>

Thanks!
--
Gustavo

> ---
>   include/linux/bpf.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/bpf.h b/include/linux/bpf.h
> index 19d8ca8ac960..1ce319045048 100644
> --- a/include/linux/bpf.h
> +++ b/include/linux/bpf.h
> @@ -2018,8 +2018,8 @@ struct bpf_prog_array {
>   };
>   
>   struct bpf_empty_prog_array {
> -	struct bpf_prog_array hdr;
>   	struct bpf_prog *null_prog;
> +	struct bpf_prog_array hdr;
>   };
>   
>   /* to avoid allocating empty bpf_prog_array for cgroups that

  reply	other threads:[~2024-10-04  1:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 18:16 [PATCH] include: linux: Fix flex array member not at the end in bpf_empty_prog_array Philipp Hortmann
2024-10-04  1:54 ` Gustavo A. R. Silva [this message]
2024-10-06 14:55 ` kernel test robot

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=674d86d6-4073-4630-b8b1-fe73ab7e995e@embeddedor.com \
    --to=gustavo@embeddedor.com \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.g.hortmann@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