Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752639AbaBYEHR (ORCPT ); Mon, 24 Feb 2014 23:07:17 -0500 Received: from mail05-md.ns.itscom.net ([175.177.155.115]:33629 "EHLO mail05-md.ns.itscom.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751866AbaBYEHP (ORCPT ); Mon, 24 Feb 2014 23:07:15 -0500 From: "J. R. Okajima" Subject: Re: [PATCH 00/13] cross rename v4 To: Miklos Szeredi Cc: Linus Torvalds , David Howells , Al Viro , Linux-Fsdevel , Kernel Mailing List , Bruce Fields , Christoph Hellwig , Andrew Morton , Zach Brown , Jan Kara , Andy Lutomirski , "mszeredi@suse.cz" In-Reply-To: <20140224171238.GG4026@tucsk.piliscsaba.szeredi.hu> References: <1391791751-2533-1-git-send-email-miklos@szeredi.hu> <19258.1392306854@warthog.procyon.org.uk> <20140213162534.GB4026@tucsk.piliscsaba.szeredi.hu> <20106.1392309770@warthog.procyon.org.uk> <16729.1392318161@warthog.procyon.org.uk> <20140224171238.GG4026@tucsk.piliscsaba.szeredi.hu> Date: Tue, 25 Feb 2014 13:07:10 +0900 Message-ID: <13532.1393301230@jrobl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Miklos Szeredi: > As Linus' suggestion, a whiteout is represented as a dummy char device. > This patch uses the 0/0 device number, but the actual number doesn't matter > as long as it doesn't conflict with a real device. I have no objection about the char device. But why do we need an inode for every whiteout? I'd suggest making a hardlink. For some filesystems which don't support hardlinks, we have to consume an inode per whiteout. But when the fs supports hardlinks, we can re-use the inode and consume a few inodes only. J. R. Okajima -- 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/