public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Kees Cook <keescook@chromium.org>,
	Xiaoming Ni <nixiaoming@huawei.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Kitt <steve@sk2.org>, Iurii Zaikin <yzaikin@google.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sysctl: const-ify ngroups_max
Date: Mon, 18 May 2020 17:25:09 +0000	[thread overview]
Message-ID: <20200518172509.GM11244@42.do-not-panic.com> (raw)
In-Reply-To: <202005180908.C016C44D2@keescook>

On Mon, May 18, 2020 at 09:08:22AM -0700, Kees Cook wrote:
> On Mon, May 18, 2020 at 05:57:27PM +0200, Stephen Kitt wrote:
> > ngroups_max is a read-only sysctl entry, reflecting NGROUPS_MAX. Make
> > it const, in the same way as cap_last_cap.
> > 
> > Signed-off-by: Stephen Kitt <steve@sk2.org>
> 
> Reviewed-by: Kees Cook <keescook@chromium.org>

Kees, since there is quite a bit of sysctl cleanup stuff going on and I
have a fs sysctl kitchen cleanup, are you alright if I carry this in a
tree and send this to Andrew once done? This would hopefully avoid
merge conflicts between these patches.

I have to still re-spin my fs sysctl stuff, but will wait to do that
once Xiaoming bases his series on linux-next.

  Luis

  reply	other threads:[~2020-05-18 17:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 15:57 [PATCH] sysctl: const-ify ngroups_max Stephen Kitt
2020-05-18 16:08 ` Kees Cook
2020-05-18 17:25   ` Luis Chamberlain [this message]
2020-05-18 18:17     ` Kees Cook
2020-05-18 18:30       ` Luis Chamberlain
2020-05-18 21:14         ` Kees Cook

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=20200518172509.GM11244@42.do-not-panic.com \
    --to=mcgrof@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nixiaoming@huawei.com \
    --cc=steve@sk2.org \
    --cc=yzaikin@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