Date: Thu, 1 Aug 2013 04:36:08 -0400
To: Christoph Hellwig <hch@infradead.org>
Cc: 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
Message-ID: <20130801083608.GJ221@brightrain.aerifal.cx>
References: <CAMbhsRQU=xrcum+ZUbG3S+JfFUJK_qm_VB96Vz=PpL=vQYhUvg@mail.gmail.com>
 <20130622103158.GA16304@infradead.org>
 <CAMbhsRTz246dWPQOburNor2HvrgbN-AWb2jT_AEywtJHFbKWsA@mail.gmail.com>
 <20130801082951.GA23563@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130801082951.GA23563@infradead.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
From: Rich Felker <dalias@aerifal.cx>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1603
Lines: 30

On Thu, Aug 01, 2013 at 01:29:51AM -0700, Christoph Hellwig wrote:
> Btw, FreeBSD has an extension to shm_open to create unnamed but fd
> passable segments.  From their man page:
> 
>     As a FreeBSD extension, the constant SHM_ANON may be used for the path
>     argument to shm_open().  In this case, an anonymous, unnamed shared
>     memory object is created.  Since the object has no name, it cannot be
>     removed via a subsequent call to shm_unlink().  Instead, the shared
>     memory object will be garbage collected when the last reference to the
>     shared memory object is removed.  The shared memory object may be shared
>     with other processes by sharing the file descriptor via fork(2) or
>     sendmsg(2).  Attempting to open an anonymous shared memory object with
>     O_RDONLY will fail with EINVAL. All other flags are ignored.
> 
> To me this sounds like the best way to expose this functionality to the
> user.  Implementing it is another question as shm_open sits in libc,
> we could either take it and shm_unlink to the kernel, or use O_TMPFILE
> on tmpfs as the backend.

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.

Rich
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/