mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Arjan van de Ven <arjanv@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] mlock-as-nonroot revisted
Date: Fri, 30 Jul 2004 04:16:39 +0200	[thread overview]
Message-ID: <20040730021639.GB30369@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.58.0407292047550.9228@dhcp030.home.surriel.com>

On Thu, Jul 29, 2004 at 08:50:16PM -0400, Rik van Riel wrote:
> please read it first, especially the changes to shmem.c ;)

I read it, and it was obviously still broken.

I got CC direct from Andrew and I read only Andrew's comment and the
code, and I could stop reading the code pretty quick since hugetlbfs is
at the top and very well visibly broken.

chown on tmpfs and hugetlbfs sounds "interesting" with your approch,
I'm looking forward to the next fixed revision. I'm not against per-user
myself, but it's not like doing it for transient memory or transient
objects associated with the task itself. Furthemore I'm not convinced
rlimits should be used for such persistent things that have nothing to
do with running tasks but ok, I can live with it if it works.

I tend to believe if something we should use fs_quota in tmpfs and
hugetlbfs for such things. That is the place to catch chown etc..

  reply	other threads:[~2004-07-30  2:17 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-29 10:03 Arjan van de Ven
2004-07-29 21:28 ` Andrew Morton
2004-07-29 21:40   ` Andrea Arcangeli
2004-07-30  0:50     ` Rik van Riel
2004-07-30  2:16       ` Andrea Arcangeli [this message]
2004-07-30  0:51   ` Rik van Riel
2004-07-30  2:17     ` Andrea Arcangeli
2004-07-30  1:52 ` Chris Wright
2004-07-30  2:09   ` Andrea Arcangeli
2004-07-30  2:46   ` Rik van Riel
2004-08-03 20:54   ` Rik van Riel
2004-08-03 21:45     ` Chris Wright
2004-08-03 20:55   ` Rik van Riel
2004-08-03 21:07     ` Andrea Arcangeli
2004-08-03 21:13       ` Arjan van de Ven
2004-08-03 21:36         ` Andrea Arcangeli
2004-08-03 21:38           ` Arjan van de Ven
2004-08-03 21:51             ` Andrea Arcangeli
2004-08-03 22:01               ` Chris Wright
2004-08-03 22:11                 ` Andrea Arcangeli
2004-08-03 22:33                   ` Chris Wright
2004-08-03 22:42                     ` Andrea Arcangeli
2004-08-03 22:52                       ` Chris Wright
2004-08-04  1:21                   ` Rik van Riel
2004-08-04  1:53                     ` Andrea Arcangeli
2004-08-04  2:01                       ` Rik van Riel
2004-08-04  2:13                         ` Andrea Arcangeli
2004-08-04  2:20                           ` William Lee Irwin III
2004-08-04  2:22                           ` Rik van Riel
2004-08-04  2:31                             ` William Lee Irwin III
2004-08-04  2:56                               ` Rik van Riel
2004-08-04  6:06                                 ` Chris Wright
2004-08-04 13:31                                   ` Rik van Riel
2004-08-04 13:51                                     ` Arjan van de Ven
2004-08-04 13:56                                       ` Rik van Riel
2004-08-04  3:13                             ` Andrea Arcangeli
2004-08-04  2:25                           ` Chris Wright
2004-08-04  2:07                       ` Chris Wright
2004-08-04  2:18                         ` Andrea Arcangeli
2004-08-03 21:13       ` Rik van Riel
2004-08-03 21:22         ` Andrea Arcangeli
2004-08-03 21:24           ` Arjan van de Ven
2004-08-03 21:31           ` Rik van Riel
2004-08-03 21:39             ` Andrea Arcangeli
2004-08-04  1:56               ` William Lee Irwin III
2004-08-03 22:18             ` Gerrit Huizenga
2004-08-04  1:22               ` Rik van Riel
2004-08-04  1:37                 ` Gerrit Huizenga
2004-08-04  1:55                   ` William Lee Irwin III

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=20040730021639.GB30369@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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

all inboxes | Powered by JetHome®