public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>
Cc: Namjae Jeon <linkinjeon@gmail.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH 0/4] fat: fix ESTALE errors
Date: Wed, 22 Aug 2012 15:17:52 +0900	[thread overview]
Message-ID: <87y5l7ih67.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <87628bjvwb.fsf@devron.myhome.or.jp> (OGAWA Hirofumi's message of "Wed, 22 Aug 2012 15:14:28 +0900")

OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:

>> I mean using a special value for this case, mark delete (using 0xe5 as
>> first character) but put for instance creation month to be egal to 15.
>>
>> This entry will be therefore be keep and not overwritten by successive
>> file creation.
>>
>> At least this solve the file deleted issue (not the rename issue unfortunatly)
>
> I assume you are saying to prevent creation somehow, not deletion. Yes, it
> is possible though, it would give additional overhead and complexity to us.

In short, it meant I think it is not so simple to do it.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2012-08-22  6:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18  9:41 [PATCH 0/4] fat: fix ESTALE errors Namjae Jeon
2012-08-18 13:25 ` Al Viro
2012-08-18 14:09   ` OGAWA Hirofumi
2012-08-20  4:19     ` Namjae Jeon
2012-08-20 20:52       ` J. Bruce Fields
2012-08-21  5:19         ` Namjae Jeon
2012-08-21  6:41           ` OGAWA Hirofumi
2012-08-21 10:58             ` Namjae Jeon
2012-08-21 21:11             ` Bastien ROUCARIES
2012-08-22  6:14               ` OGAWA Hirofumi
2012-08-22  6:17                 ` OGAWA Hirofumi [this message]
2012-08-21 13:20         ` Steven J. Magnani
2012-08-21 18:02           ` Ravishankar
2012-08-20  4:21   ` 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=87y5l7ih67.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --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=roucaries.bastien@gmail.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