On Thu, Jan 30, 2014 at 10:42 PM, John Stultz <john.stultz@xxxxxxxxxx> wrote: > On 01/30/2014 08:02 AM, Kay Sievers wrote: >> On Thu, Jan 30, 2014 at 9:46 AM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: >>> On Mon, Jan 27, 2014 at 05:37:04PM -0800, John Stultz wrote: >>>> In working with ashmem and looking briefly at kdbus' memfd ideas, >>>> there's a commonality that both basically act as a method to provide >>>> applications with unlinked tmpfs/shmem fds. >>> Just use O_TMPFILE on a tmpfs file and you're done. >> Ashmem and kdbus can name the deleted files, which is useful for >> debugging and tools to show the associated name for the file >> descriptor. They also show up in /proc/$PID/maps/ and possibly in >> /proc/$PID/fd/. >> >> O_TMPFILE always creates files with just the name "/". Unless that is >> changed we wouldn't want switch over to O_TMPFILE, because we would >> lose that nice feature. > > Not sure, but would Colin's vma-naming patch (or something like it) help > address this? > https://lkml.org/lkml/2013/10/30/518 Hmm, I don't think so, this seems to be about anonymous memory only, but shmem files are not anonymous. We actually just really want the actual file names, ashmem too, like shmem_file_setup() accepts the name for the unlinked file to create. Kay -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>