From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Alejandro Martinez Ruiz <alex@nowcomputing.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: f2fs backport and typo fix
Date: Tue, 29 Jan 2013 20:43:23 +0900 [thread overview]
Message-ID: <1359459803.22847.51.camel@kjgkr> (raw)
In-Reply-To: <1359375114-6269-1-git-send-email-alex@nowcomputing.com>
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Hi,
2013-01-28 (월), 13:11 +0100, Alejandro Martinez Ruiz:
> Hi,
>
> I recently ported f2fs to kernel 3.2, but I am not sure whether the changes are
> all OK. If so, that could be useful to a number of projects, and I'd very much
> appreciate any help in reviewing and looking for possible errors or omissions,
> specially those related to VFS.
Great job. Thank you for the work.
BTW, as I see your patches in the repo, it would be better to modify the
following patch.
Except this, everything looks good to me at a glance.
0002-vfs-export-symbol-d_find_any_alias.patch
- Let's avoid modifying the kernel core.
@@ -104,19 +102,14 @@ static int need_to_sync_dir(struct f2fs_sb_info
*sbi, struct inode *inode)
struct dentry *dentry;
nid_t pino;
- inode = igrab(inode);
- dentry = d_find_any_alias(inode);
- if (!dentry) {
- iput(inode);
+ dentry = list_entry(inode->i_dentry.next, struct dentry,
d_alias);
+ if (!dentry)
return 0;
- }
pino = dentry->d_parent->d_inode->i_ino;
- dput(dentry);
- iput(inode);
return !is_checkpointed_node(sbi, pino);
}
>
> You can check the 3.2 kernel patches in http://github.com/nowcomputing/f2fs-backports.
>
> Additionally, I just noticed a typo in f2fs options. Here's a patch for use with
> git am --scissors.
Applied, thank you~ :)
--
Jaegeuk Kim
Samsung
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-29 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 12:11 f2fs backport and typo fix Alejandro Martinez Ruiz
2013-01-29 11:43 ` Jaegeuk Kim [this message]
2013-01-29 14:08 ` Alejandro Martinez
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=1359459803.22847.51.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=alex@nowcomputing.com \
--cc=linux-fsdevel@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 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).