Linux filesystem development
 help / color / mirror / Atom feed
From: "Lukáš Czerner" <lczerner@redhat.com>
To: chishanmingshen <chishanmingshen@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC 1/1] vfs: del redundant BH_new flag on unrelated buffer heads.
Date: Mon, 23 Jun 2014 11:08:31 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1406231102360.2169@localhost.localdomain> (raw)
In-Reply-To: <1401969309-3734-1-git-send-email-chishanmingshen@gmail.com>

On Thu, 5 Jun 2014, chishanmingshen wrote:

> Date: Thu,  5 Jun 2014 19:55:09 +0800
> From: chishanmingshen <chishanmingshen@gmail.com>
> To: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: linux-fsdevel@vger.kernel.org, chishanmingshen <chishanmingshen@gmail.com>
> Subject: [RFC 1/1] vfs: del redundant BH_new flag on unrelated buffer heads.
> 
> Just skip the unrelated buffer heads when clear buffer head's BH_new flag.

I can see that from the code, but can you explain why in the commit
description ?

Thanks!
-Lukas

> This patch is *untested*.
> 
> Signed-off-by: chishanmingshen <chishanmingshen@gmail.com>
> ---
>  fs/buffer.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/buffer.c b/fs/buffer.c
> index 9ddb9fc..a28a1a1 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -1987,8 +1987,8 @@ static int __block_commit_write(struct inode *inode, struct page *page,
>  		} else {
>  			set_buffer_uptodate(bh);
>  			mark_buffer_dirty(bh);
> +			clear_buffer_new(bh);
>  		}
> -		clear_buffer_new(bh);
>  
>  		block_start = block_end;
>  		bh = bh->b_this_page;
> 

  reply	other threads:[~2014-06-23  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 11:55 [RFC 1/1] vfs: del redundant BH_new flag on unrelated buffer heads chishanmingshen
2014-06-23  9:08 ` Lukáš Czerner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-06  9:31 chishanmingshen

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=alpine.LFD.2.00.1406231102360.2169@localhost.localdomain \
    --to=lczerner@redhat.com \
    --cc=chishanmingshen@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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