From: Willy Tarreau <w@1wt.eu>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Eric Paris <eparis@redhat.com>,
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: Fri, 21 Dec 2007 22:16:02 +0100 [thread overview]
Message-ID: <20071221211602.GA14811@1wt.eu> (raw)
In-Reply-To: <Pine.LNX.4.64.0712212209240.11671@fbirervta.pbzchgretzou.qr>
Hi Jan,
On Fri, Dec 21, 2007 at 10:10:24PM +0100, Jan Engelhardt wrote:
>
> On Dec 21 2007 15:31, Eric Paris wrote:
> >On Thu, 2007-12-20 at 00:29 +0100, Jan Engelhardt wrote:
> >> On Dec 19 2007 16:59, Eric Paris wrote:
> >> >
> >> >+config SECURITY_DEFAULT_MMAP_MIN_ADDR
> >> >+ int "Low address space to protect from user allocation"
> >>
> >> Hm, should not this be 'hex'?
> >
> >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.
While most of us have no problem doing an instant conversion, many
people will find it painful to convert the output of cat before copying
it into their .config.
I'm generally for hex, but here I'd prefer to stay with the in-place
format which is already decimal. And as you said, people can still
write the hex value into /proc/sys if they want to.
Regards,
Willy
next prev parent reply other threads:[~2007-12-21 21:18 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 [this message]
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
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=20071221211602.GA14811@1wt.eu \
--to=w@1wt.eu \
--cc=akpm@linux-foundation.org \
--cc=alan@redhat.com \
--cc=chrisw@redhat.com \
--cc=eparis@redhat.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=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.