public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Andreas Gruenbacher <agruenba@redhat.com>,
	Daniel Verkamp <dverkamp@chromium.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Jeff Xu <jeffxu@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Boqun Feng <boqun.feng@gmail.com>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Frederic Weisbecker <frederic@kernel.org>,
	syzbot+ac3b41786a2d0565b6d5@syzkaller.appspotmail.com,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] pid: Replace struct pid 1-element array with flex-array
Date: Thu, 18 May 2023 17:07:09 +0200	[thread overview]
Message-ID: <20230518-jemand-ehrte-80f8b538ca03@brauner> (raw)
In-Reply-To: <20230517225838.never.965-kees@kernel.org>

On Wed, 17 May 2023 15:58:42 -0700, Kees Cook wrote:
> For pid namespaces, struct pid uses a dynamically sized array member,
> "numbers". This was implemented using the ancient 1-element fake flexible
> array, which has been deprecated for decades. Replace it with a C99
> flexible array, refactor the array size calculations to use struct_size(),
> and address elements via indexes. Note that the static initializer (which
> defines a single element) works as-is, and requires no special handling.
> 
> [...]

Applied to the kernel.fork branch of the brauner/linux.git tree.
Patches in the kernel.fork branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git
branch: kernel.fork

[1/1] pid: Replace struct pid 1-element array with flex-array
      https://git.kernel.org/brauner/linux/c/ad0ff58dc959

  parent reply	other threads:[~2023-05-18 15:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 22:58 [PATCH] pid: Replace struct pid 1-element array with flex-array Kees Cook
2023-05-18 14:48 ` Christian Brauner
2023-05-18 15:07 ` Christian Brauner [this message]
2023-05-30 14:44   ` Jeff Xu

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=20230518-jemand-ehrte-80f8b538ca03@brauner \
    --to=brauner@kernel.org \
    --cc=agruenba@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=boqun.feng@gmail.com \
    --cc=dverkamp@chromium.org \
    --cc=frederic@kernel.org \
    --cc=jack@suse.cz \
    --cc=jeffxu@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=syzbot+ac3b41786a2d0565b6d5@syzkaller.appspotmail.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