From: Eric Paris <eparis@redhat.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Greg KH <greg@kroah.com>, Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org, jmorris@namei.org, alan@redhat.com,
chrisw@redhat.com, akpm@linux-foundation.org,
linux-security-module@vger.kernel.org, solar@openwall.com,
wtarreau@hera.kernel.org
Subject: Re: [PATCH] Allow Kconfig to set default mmap_min_addr protection
Date: Wed, 02 Jan 2008 12:09:31 -0500 [thread overview]
Message-ID: <1199293771.3716.21.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0712212358440.25803@fbirervta.pbzchgretzou.qr>
On Fri, 2007-12-21 at 23:59 +0100, Jan Engelhardt wrote:
> On Dec 21 2007 14:35, Greg KH wrote:
> >> >> >I guess it could be, but the input for /proc/sys/vm/mmap_min_addr is
> >> >> >base 10 as well
> >> >>
> >> >> sysfs is autobase, i.e. echo "0xb000" >/sys/foo will Do The Right Thing.
> >> >
> >> >yes but if you cat /proc/sys/vm/mmap_min_addr, it returns in base 10.
> >>
> >> sysfs should probably be tuned to output it in a preferred base.
> >
> >Again, this is sysctl, not sysfs. two very different things...
> >
> Argh... :) Just shows that /proc is the wrong place for system variables.
>
> Well, module_params(integer) are autobase, and that's all I needed so
> far :-D
So in the end we are all happy with the original patch I sent?
-Eric
next prev parent reply other threads:[~2008-01-02 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 21:59 [PATCH] Allow Kconfig to set default mmap_min_addr protection Eric Paris
2007-12-19 23:29 ` Jan Engelhardt
2007-12-21 20:31 ` Eric Paris
2007-12-21 21:10 ` Jan Engelhardt
2007-12-21 21:16 ` Willy Tarreau
2007-12-21 22:04 ` Jan Engelhardt
2007-12-21 22:35 ` Greg KH
2007-12-21 22:59 ` Jan Engelhardt
2008-01-02 17:09 ` Eric Paris [this message]
2008-01-02 17:26 ` Jan Engelhardt
2008-01-02 18:10 ` Willy Tarreau
2007-12-21 22:34 ` Greg KH
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=1199293771.3716.21.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=chrisw@redhat.com \
--cc=greg@kroah.com \
--cc=jengelh@computergmbh.de \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=solar@openwall.com \
--cc=w@1wt.eu \
--cc=wtarreau@hera.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.