Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752482Ab3FXR07 (ORCPT ); Mon, 24 Jun 2013 13:26:59 -0400 Received: from mail-vb0-f44.google.com ([209.85.212.44]:48651 "EHLO mail-vb0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751506Ab3FXR06 (ORCPT ); Mon, 24 Jun 2013 13:26:58 -0400 MIME-Version: 1.0 In-Reply-To: <20130624114832.GA9961@infradead.org> References: <20130622103158.GA16304@infradead.org> <20130624114832.GA9961@infradead.org> Date: Mon, 24 Jun 2013 10:26:57 -0700 Message-ID: Subject: Re: RFC: named anonymous vmas From: Colin Cross To: Christoph Hellwig Cc: Alex Elsayed , Linux-MM , lkml Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 986 Lines: 18 On Mon, Jun 24, 2013 at 4:48 AM, Christoph Hellwig wrote: > On Sat, Jun 22, 2013 at 12:47:29PM -0700, Alex Elsayed wrote: >> Couldn't this be done by having a root-only tmpfs, and having a userspace >> component that creates per-app directories with restrictive permissions on >> startup/app install? Then each app creates files in its own directory, and >> can pass the fds around. If each app gets its own writable directory that's not really different than a world writable tmpfs. It requires something that watches for apps to exit for any reason and cleans up their directories, and it requires each app to come up with an unused name when it wants to create a file, and the kernel can give you both very cleanly. -- 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/