From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
Amit Sahrawat <amit.sahrawat83@gmail.com>
Subject: Re: [PATCH 3/3] fat: simplify writeback_inode function.
Date: Sun, 26 Aug 2012 23:05:42 +0900 [thread overview]
Message-ID: <874nnpwxxl.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1345883026-6297-1-git-send-email-linkinjeon@gmail.com> (Namjae Jeon's message of "Sat, 25 Aug 2012 04:23:46 -0400")
Namjae Jeon <linkinjeon@gmail.com> writes:
> Simplify writeback_inode function.
Looks cleanup without logic change.
Acked-by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
> Signed-off-by: Namjae Jeon <linkinjeon@gmail.com>
> Signed-off-by: Amit Sahrawat <amit.sahrawat83@gmail.com>
> ---
> fs/fat/inode.c | 14 +++++---------
> 1 file changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/fs/fat/inode.c b/fs/fat/inode.c
> index 973296b..4bbb24e 100644
> --- a/fs/fat/inode.c
> +++ b/fs/fat/inode.c
> @@ -1457,18 +1457,14 @@ static int writeback_inode(struct inode *inode)
> {
>
> int ret;
> - struct address_space *mapping = inode->i_mapping;
> - struct writeback_control wbc = {
> - .sync_mode = WB_SYNC_NONE,
> - .nr_to_write = 0,
> - };
> - /* if we used WB_SYNC_ALL, sync_inode waits for the io for the
> - * inode to finish. So WB_SYNC_NONE is sent down to sync_inode
> +
> + /* if we used wait=1, sync_inode_metadata waits for the io for the
> + * inode to finish. So wait=0 is sent down to sync_inode_metadata
> * and filemap_fdatawrite is used for the data blocks
> */
> - ret = sync_inode(inode, &wbc);
> + ret = sync_inode_metadata(inode, 0);
> if (!ret)
> - ret = filemap_fdatawrite(mapping);
> + ret = filemap_fdatawrite(inode->i_mapping);
> return ret;
> }
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2012-08-26 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-25 8:23 Namjae Jeon
2012-08-26 14:05 ` OGAWA Hirofumi [this message]
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=874nnpwxxl.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=amit.sahrawat83@gmail.com \
--cc=linkinjeon@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®