Linux EXT4 FS development
 help / color / mirror / Atom feed
From: "Lukáš Czerner" <lczerner@redhat.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
	Ted Tso <tytso@mit.edu>,
	linux-ext4@vger.kernel.org,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] ext4: pair trace_ext4_writepages & trace_ext4_writepages_result
Date: Thu, 17 Oct 2013 15:31:34 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1310171531040.3212@localhost.localdomain> (raw)
In-Reply-To: <1382012926-398-1-git-send-email-ming.lei@canonical.com>

On Thu, 17 Oct 2013, Ming Lei wrote:

> Date: Thu, 17 Oct 2013 20:28:46 +0800
> From: Ming Lei <ming.lei@canonical.com>
> To: linux-kernel@vger.kernel.org
> Cc: Jan Kara <jack@suse.cz>, Ming Lei <ming.lei@canonical.com>,
>     Ted Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org,
>     "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
> Subject: [PATCH] ext4: pair trace_ext4_writepages &
>     trace_ext4_writepages_result
> 
> Pair the two trace events to make troubeshooting writepages
> easier, and it should be more convinient to write a simple script
> to parse the traces.
> 
> Cc: Ted Tso <tytso@mit.edu>
> Cc: linux-ext4@vger.kernel.org
> Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
> Cc: Jan Kara <jack@suse.cz>
> Signed-off-by: Ming Lei <ming.lei@canonical.com>

It looks good.

Thanks!

Reviewed-by: Lukas Czerner <lczerner@redhat.com>

> ---
>  fs/ext4/inode.c |   11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index 32beaa4..0ad73d4 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -2420,16 +2420,15 @@ static int ext4_writepages(struct address_space *mapping,
>  	 * because that could violate lock ordering on umount
>  	 */
>  	if (!mapping->nrpages || !mapping_tagged(mapping, PAGECACHE_TAG_DIRTY))
> -		return 0;
> +		goto out_writepages;
>  
>  	if (ext4_should_journal_data(inode)) {
>  		struct blk_plug plug;
> -		int ret;
>  
>  		blk_start_plug(&plug);
>  		ret = write_cache_pages(mapping, wbc, __writepage, mapping);
>  		blk_finish_plug(&plug);
> -		return ret;
> +		goto out_writepages;
>  	}
>  
>  	/*
> @@ -2442,8 +2441,10 @@ static int ext4_writepages(struct address_space *mapping,
>  	 * *never* be called, so if that ever happens, we would want
>  	 * the stack trace.
>  	 */
> -	if (unlikely(sbi->s_mount_flags & EXT4_MF_FS_ABORTED))
> -		return -EROFS;
> +	if (unlikely(sbi->s_mount_flags & EXT4_MF_FS_ABORTED)) {
> +		ret = -EROFS;
> +		goto out_writepages;
> +	}
>  
>  	if (ext4_should_dioread_nolock(inode)) {
>  		/*
> 

  reply	other threads:[~2013-10-17 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-17 12:28 [PATCH] ext4: pair trace_ext4_writepages & trace_ext4_writepages_result Ming Lei
2013-10-17 13:31 ` Lukáš Czerner [this message]
2013-10-30 11:36 ` Theodore Ts'o

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.1310171531040.3212@localhost.localdomain \
    --to=lczerner@redhat.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=tytso@mit.edu \
    /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