From mboxrd@z Thu Jan 1 00:00:00 1970 From: hooanon05@yahoo.co.jp Subject: Re: [RFC PATCH 0/2] Union Mount: Directory listing in glibc Date: Wed, 30 Apr 2008 00:21:09 +0900 Message-ID: <9167.1209482469@jrobl> References: <20080429133201.GA9938@localhost.localdomain> Cc: libc-alpha@sourceware.org, Jan Blunck , Erez Zadok , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk, Christoph Hellwig , Ulrich Drepper , Mingming Cao , Dave Hansen , Trond Myklebust , bharata@linux.vnet.ibm.com, David Woodhouse To: bsn.0007@gmail.com Return-path: Received: from vsmtp02.dti.ne.jp ([202.216.231.137]:53930 "EHLO vsmtp02.dti.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751682AbYD2PYM (ORCPT ); Tue, 29 Apr 2008 11:24:12 -0400 In-Reply-To: <20080429133201.GA9938@localhost.localdomain> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hello Nagabhushan, bsn.0007@gmail.com: > I went through Bharata's RFC post on glibc based Union Mount readdir solution > (http://lkml.org/lkml/2008/3/11/34) and have come up with patches > against glibc to implement the same. ::: While I don't have objection against the implementation in userspace, what will UnionMount handle about rmdir or rename dir? Those systemcalls need to test whether the dir is *logically* empty or not in kernel space, don't they? And I am afraid that UnionMount has to implement the similar thing, but it never mean to modify glibc is a bad idea. Junjiro Okajima