From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] f2fs: update file name in the inode block during f2fs_rename
Date: Thu, 18 Jul 2013 10:22:12 +0100 [thread overview]
Message-ID: <20130718092211.GA4165@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1374138684-28520-1-git-send-email-jaegeuk.kim@samsung.com>
On Thu, Jul 18, 2013 at 06:11:23PM +0900, Jaegeuk Kim wrote:
> The error is reproducible by:
>
> After this, when we retrieve the inode->i_name of test2 by dump.f2fs, we get
> test1 instead of test2.
> This is because f2fs didn't update the file name during the f2fs_rename.
Er... Correct me if I'm wrong, but f2fs appears to support link(2) and
if rename(2) creates some problem for dump.f2fs, I would expect an
equivalent link()+unlink() combination to do the same...
next prev parent reply other threads:[~2013-07-18 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 9:11 [f2fs-dev] [PATCH] f2fs: update file name in the inode block during f2fs_rename Jaegeuk Kim
2013-07-18 9:11 ` Jaegeuk Kim
2013-07-18 9:22 ` Al Viro [this message]
2013-07-19 3:40 ` [f2fs-dev] " Kim Jaegeuk
2013-07-19 7:49 ` Al Viro
2013-07-19 7:49 ` Al Viro
2013-07-22 13:24 ` Jaegeuk Kim
2013-07-22 13:24 ` Jaegeuk Kim
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=20130718092211.GA4165@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.