From: John Stultz <john.stultz@linaro.org>
To: "H. Peter Anvin" <hpa@zytor.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Greg KH <gregkh@linuxfoundation.org>, Kay Sievers <kay@vrfy.org>,
Android Kernel Team <kernel-team@android.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>,
Dave Hansen <dave.hansen@intel.com>,
Rik van Riel <riel@redhat.com>,
Michel Lespinasse <walken@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Neil Brown <neilb@suse.de>,
Andrea Arcangeli <aarcange@redhat.com>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
Minchan Kim <minchan@kernel.org>,
Lennart Poettering <mzxreary@0pointer.de>
Subject: Re: [RFC] shmgetfd idea
Date: Tue, 28 Jan 2014 11:56:53 -0800 [thread overview]
Message-ID: <52E80B85.8020302@linaro.org> (raw)
In-Reply-To: <52E7298D.5020001@zytor.com>
On 01/27/2014 07:52 PM, H. Peter Anvin wrote:
> On 01/27/2014 05:37 PM, John Stultz wrote:
>> In the Android case, its important to have this interface to atomically
>> provide these unlinked tmpfs fds, because they'd like to avoid having
>> tmpfs mounts that are writable by applications (since that creates a
>> potential DOS on the system by applications writing random files that
>> persist after the process has been killed). It also provides better
>> life-cycle management for resources, since as the fds never have named
>> links in the filesystem, their resources are automatically cleaned up
>> when the last process with the fd dies, and there's no potential races
>> between create and unlink with processes being terminated, which avoids
>> the need for cleanup management.
>>
> What about if tmpfs could be restricted to only only O_TMPFILE open()s?
> This pretty much amounts to an option to prevent tmpfs from creating
> new directory entries.
Thanks for reminding me about O_TMPFILE.. I have it on my list to look
into how it could be used.
As for the O_TMPFILE only tmpfs option, it seems maybe a little clunky
to me, but possible. If others think this would be preferred over a new
syscall, I'll dig in deeper.
thanks
-john
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-01-28 19:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 1:37 [RFC] shmgetfd idea John Stultz
2014-01-28 1:53 ` Kay Sievers
2014-01-28 19:47 ` John Stultz
2014-01-28 3:52 ` H. Peter Anvin
2014-01-28 19:56 ` John Stultz [this message]
2014-01-28 20:37 ` H. Peter Anvin
2014-01-28 20:58 ` John Stultz
2014-01-28 21:01 ` Kay Sievers
2014-01-28 21:05 ` John Stultz
2014-01-28 21:10 ` H. Peter Anvin
2014-01-28 21:54 ` John Stultz
2014-01-28 22:14 ` Kay Sievers
2014-01-28 23:02 ` H. Peter Anvin
2014-01-28 23:14 ` Kay Sievers
2014-01-28 23:19 ` H. Peter Anvin
2014-01-29 0:14 ` Kay Sievers
2014-01-29 0:20 ` H. Peter Anvin
2014-01-29 0:49 ` Kay Sievers
2014-01-28 23:14 ` John Stultz
2014-01-28 21:28 ` Kay Sievers
2014-01-30 8:46 ` Christoph Hellwig
2014-01-30 16:02 ` Kay Sievers
2014-01-30 21:42 ` John Stultz
2014-01-31 0:01 ` Kay Sievers
2014-02-03 15:03 ` Christoph Hellwig
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=52E80B85.8020302@linaro.org \
--to=john.stultz@linaro.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=kay@vrfy.org \
--cc=kernel-team@android.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mzxreary@0pointer.de \
--cc=neilb@suse.de \
--cc=riel@redhat.com \
--cc=takahiro.akashi@linaro.org \
--cc=walken@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 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.