From: Christoph Hellwig <hch@infradead.org>
To: Rich Felker <dalias@aerifal.cx>
Cc: Christoph Hellwig <hch@infradead.org>,
Colin Cross <ccross@google.com>,
lkml <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>,
Android Kernel Team <kernel-team@android.com>,
John Stultz <john.stultz@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: RFC: named anonymous vmas
Date: Fri, 2 Aug 2013 08:11:41 -0700 [thread overview]
Message-ID: <20130802151141.GA4439@infradead.org> (raw)
In-Reply-To: <20130801083608.GJ221@brightrain.aerifal.cx>
On Thu, Aug 01, 2013 at 04:36:08AM -0400, Rich Felker wrote:
> I'm not sure what the purpose is. shm_open with a long random filename
> and O_EXCL|O_CREAT, followed immediately by shm_unlink, is just as
> good except in the case where you have a malicious user killing the
> process in between these two operations.
The Android people already have an shm API doesn't leave traces in the
filesystem, and I at least conceptually agree that having an API that
doesn't introduce posisble other access is a good idea. This is the
same reason why the O_TMPFILE API was added in this releases.
next prev parent reply other threads:[~2013-08-02 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 23:42 RFC: named anonymous vmas Colin Cross
2013-06-22 5:12 ` Kyungmin Park
2013-06-22 5:20 ` Colin Cross
2013-06-22 10:31 ` Christoph Hellwig
2013-06-22 17:30 ` Colin Cross
[not found] ` <kq4v0b$p8p$3@ger.gmane.org>
2013-06-24 11:48 ` Christoph Hellwig
2013-06-24 17:26 ` Colin Cross
2013-06-24 23:45 ` John Stultz
2013-07-14 0:57 ` Sam Ben
2013-08-01 8:29 ` Christoph Hellwig
2013-08-01 8:36 ` Rich Felker
2013-08-02 15:11 ` Christoph Hellwig [this message]
2013-08-03 23:54 ` KOSAKI Motohiro
2013-07-14 0:27 ` Sam Ben
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=20130802151141.GA4439@infradead.org \
--to=hch@infradead.org \
--cc=ccross@google.com \
--cc=dalias@aerifal.cx \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).