mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joel Granados <j.granados@samsung.com>
To: Kees Cook <keescook@chromium.org>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Luis Chamberlain" <mcgrof@kernel.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] sysctl: constify ctl_table arguments of utility function
Date: Tue, 14 May 2024 15:40:04 +0200	[thread overview]
Message-ID: <20240514134004.vrykjaynv2f5p2fx@joelS2.panther.com> (raw)
In-Reply-To: <202405131246.C27D85E1@keescook>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 964 bytes --]

On Mon, May 13, 2024 at 12:47:07PM -0700, Kees Cook wrote:
> On Mon, May 13, 2024 at 11:25:18AM +0200, Joel Granados via B4 Relay wrote:
> > From: Thomas Weißschuh <linux@weissschuh.net>
> > 
> > In a future commit the proc_handlers themselves will change to
> > "const struct ctl_table". As a preparation for that adapt the internal
> > helper.
> > 
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> 
> Yup, looks good. At what point is this safe to apply to Linus's tree?
> i.e. what prerequisite patches need to land before this?

I was planning to queue this for v6.11. I expect the other patches (1/11 - 9/11)
will make it to mainline at that point.

This patchset has no dependencies and can easily go into v6.11 as it is trivial,
the generated assember (in x86_64 at least) is unchanged and it has been tested
it in 0-day.

> 
> Reviewed-by: Kees Cook <keescook@chromium.org>
> 
> -- 
> Kees Cook

-- 

Joel Granados

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2024-05-15  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-13  9:25 Joel Granados via B4 Relay
2024-05-13 19:47 ` Kees Cook
2024-05-14 13:40   ` Joel Granados [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=20240514134004.vrykjaynv2f5p2fx@joelS2.panther.com \
    --to=j.granados@samsung.com \
    --cc=keescook@chromium.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=mcgrof@kernel.org \
    /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

all inboxes | Powered by JetHome®