From: Rohit Seth <rseth@unix-os.sc.intel.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Andrew Morton <akpm@digeo.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] remove hugetlb syscalls
Date: Thu, 14 Nov 2002 13:40:25 -0800 [thread overview]
Message-ID: <3DD41849.20306@unix-os.sc.intel.com> (raw)
In-Reply-To: <20021114161134.E20258@redhat.com>
Benjamin LaHaise wrote:
>Oracle does not run as root, so they can't even use the syscalls
>directly. At least with hugetlbfs we can chmod the filesystem to be
>owned by the oracle user.
>
> -ben
>
>
>
Strictly speaking user don't have to be root. Currently the syscall
only requires users to have root as one of the supplementary groups (and
that is how Oracle is actually using these syscalls). And if
CAP_IPC_LOCK (to make it coherent with fs side of the world) is what is
preferdto provide access to hugepages then that change is simple also.
Don't need to do any chmod.
rohit
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-11-14 21:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-13 23:45 Benjamin LaHaise
2002-11-14 0:42 ` Rik van Riel
2002-11-14 8:52 ` dada1
2002-11-14 14:13 ` Christoph Hellwig
2002-11-14 15:13 ` dada1
2002-11-14 15:31 ` Benjamin LaHaise
2002-11-14 15:38 ` dada1
[not found] ` <3DD3FED2.2010901@unix-os.sc.intel.com>
2002-11-14 20:01 ` Benjamin LaHaise
2002-11-14 21:06 ` Benjamin LaHaise
2002-11-14 20:11 ` Rohit Seth
2002-11-14 20:36 ` William Lee Irwin III
2002-11-14 20:30 ` William Lee Irwin III
2002-11-14 20:48 ` Benjamin LaHaise
2002-11-14 21:02 ` William Lee Irwin III
2002-11-14 21:11 ` Benjamin LaHaise
2002-11-14 21:31 ` William Lee Irwin III
2002-11-14 21:40 ` Rohit Seth [this message]
2002-11-14 21:59 ` Benjamin LaHaise
2002-11-14 21:06 ` Benjamin LaHaise
2002-11-14 21:06 ` Benjamin LaHaise
2002-11-14 22:12 Seth, Rohit
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=3DD41849.20306@unix-os.sc.intel.com \
--to=rseth@unix-os.sc.intel.com \
--cc=akpm@digeo.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.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