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