From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: *at syscalls for xattrs? Date: Mon, 16 Jul 2007 09:04:02 +0100 Message-ID: <20070716080401.GI21668@ftp.linux.org.uk> References: <20070715205313.GE21668@ftp.linux.org.uk> <1184534001.2765.5.camel@entropy> <20070715222323.GG21668@ftp.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Nicholas Miell , linux-fsdevel@vger.kernel.org, Linux Kernel Mailing List To: Jan Engelhardt Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:56172 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752004AbXGPIED (ORCPT ); Mon, 16 Jul 2007 04:04:03 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Jul 16, 2007 at 09:56:10AM +0200, Jan Engelhardt wrote: > >Just one question: what the bleeding hell for? Not that the rest of > >..at() family made any damn sense as an interface... > > fd1 = open("dir1", O_DIRECTORY): > fd2 = open("dir2", O_DIRECTORY); > system("mount -t tmpfs none dir1"); > system("mount -t tmpfs none dir2"); > openat(fd1, "file1", O_RDWR | O_CREAT); > openat(fd2, "file2", O_RDWR | O_CREAT); > > If you have a better way to accomplish this, let me know. :) To accomplish what, exactly? Access to overmounted directory? So bind it elsewhere and use that. I still don't see the point - neither of the interface nor of your example...