[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fw6x90o3.fsf@devron.myhome.or.jp>
Date: Wed, 05 Sep 2012 02:07:40 +0900
From: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To: Namjae Jeon <linkinjeon@...il.com>
Cc: akpm@...ux-foundation.org, bfields@...ldses.org,
viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
Namjae Jeon <namjae.jeon@...sung.com>,
Ravishankar N <ravi.n1@...sung.com>,
Amit Sahrawat <a.sahrawat@...sung.com>
Subject: Re: [PATCH v2 4/5] fat: eliminate orphaned inode number allocation
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> writes:
> Namjae Jeon <linkinjeon@...il.com> writes:
>
>> From: Namjae Jeon <namjae.jeon@...sung.com>
>>
>> Maintain a list of inode(i_pos) numbers of orphaned inodes (i.e the
>> inodes that have been unlinked but still having open file
>> descriptors).At file/directory creation time, skip using such i_pos
>> values.Removal of the i_pos from the list is done during inode eviction.
>
> What happens if the directory (has busy entries) was completely removed?
>
>
> And Al's point is important for NFS too. If you want stable ino for NFS,
> you never can't change it.
s/never can't/never can/
--
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists