From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, bfields@fieldses.org,
viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
Namjae Jeon <namjae.jeon@samsung.com>,
Ravishankar N <ravi.n1@samsung.com>,
Amit Sahrawat <a.sahrawat@samsung.com>
Subject: Re: [PATCH v2 4/5] fat: eliminate orphaned inode number allocation
Date: Wed, 05 Sep 2012 02:07:40 +0900 [thread overview]
Message-ID: <87fw6x90o3.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <87mx15910k.fsf@devron.myhome.or.jp> (OGAWA Hirofumi's message of "Wed, 05 Sep 2012 02:00:11 +0900")
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:
> Namjae Jeon <linkinjeon@gmail.com> writes:
>
>> From: Namjae Jeon <namjae.jeon@samsung.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@mail.parknet.co.jp>
next prev parent reply other threads:[~2012-09-04 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 15:58 [PATCH v2 4/5] fat: eliminate orphaned inode number allocation Namjae Jeon
2012-09-04 17:00 ` OGAWA Hirofumi
2012-09-04 17:07 ` OGAWA Hirofumi [this message]
2012-09-04 18:38 ` J. Bruce Fields
2012-09-04 19:02 ` OGAWA Hirofumi
2012-09-04 19:25 ` J. Bruce Fields
2012-09-04 20:45 ` NeilBrown
2012-09-05 13:37 ` Namjae Jeon
2012-09-05 13:56 ` OGAWA Hirofumi
2012-09-06 6:30 ` Namjae Jeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fw6x90o3.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=linkinjeon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=ravi.n1@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).