linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Iurii Zaikin <yzaikin@google.com>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	linux-mm@kvack.org, Ivan Teterevkov <ivan.teterevkov@nutanix.com>,
	Michal Hocko <mhocko@kernel.org>,
	David Rientjes <rientjes@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	"Eric W . Biederman" <ebiederm@xmission.com>
Subject: Re: [RFC] kernel/sysctl: support setting sysctl parameters from kernel command line
Date: Tue, 24 Mar 2020 11:24:17 -0700	[thread overview]
Message-ID: <202003241121.44E725B@keescook> (raw)
In-Reply-To: <bc721358-6202-bdc5-0398-29921b3f9855@suse.cz>

On Tue, Mar 24, 2020 at 05:50:49PM +0100, Vlastimil Babka wrote:
> On 3/17/20 10:29 PM, Kees Cook wrote:
> > mm.transparent_hugepage.enabled
> 
> Hm, transparent_hugepage is in sysfs (/sys/kernel/mm), but not sysctl, at least
> in my case the sysctl tool doesn't list it. Yours does? Yay for consistency.

Oh, whoops! That was my mistake; my eyes skipped out of /proc/sys ;)

> > I like the idea if just for having to build less boiler plate for
> > supporting things that I've had to plumb to both boot_params and sysctl.
> > :)
> 
> Thanks, I will pursue the idea further then :)

Awesome! I've wanted this for a long time but never had the time to give
it a try. :)

-- 
Kees Cook

      reply	other threads:[~2020-03-24 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-17 13:21 [RFC] kernel/sysctl: support setting sysctl parameters from kernel command line Vlastimil Babka
2020-03-17 21:29 ` Kees Cook
2020-03-24 16:50   ` Vlastimil Babka
2020-03-24 18:24     ` Kees Cook [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=202003241121.44E725B@keescook \
    --to=keescook@chromium.org \
    --cc=ebiederm@xmission.com \
    --cc=ivan.teterevkov@nutanix.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mcgrof@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=rientjes@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).