linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Czerner <lczerner@redhat.com>
To: Lukas Czerner <lczerner@redhat.com>
Cc: tytso@mit.edu, sandeen@redhat.com, linux-fsdevel@vger.kernel.org,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Remove warning message from ext4_issue_discard helper
Date: Mon, 20 Dec 2010 12:19:44 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1012201218470.12772@dhcp-lab-213.englab.brq.redhat.com> (raw)
In-Reply-To: <1290537723-18558-1-git-send-email-lczerner@redhat.com>

On Tue, 23 Nov 2010, Lukas Czerner wrote:

> ext4_issue_discard is supposed to be helper for calling discard, however
> in case that underlying device does not support discard it prints out
> the warning message and clears the DISCARD t_mount_opt flag. Since it
> can be (and is) used by others, it should not do anything and let the
> caller to handle the error case.
> 
> This commit removes warning message and flag setting from
> ext4_issue_discard and use it just in place where it is really needed
> (release_blocks_on_commit). FITRIM ioctl should not set any flags nor it
> should print out warning messages, so get rid of the warning as well.
> 
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
> ---
>  fs/ext4/mballoc.c |   22 ++++++++++------------
>  1 files changed, 10 insertions(+), 12 deletions(-)
> 
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 5b4d4e3..e479319 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -2608,18 +2608,12 @@ int ext4_mb_release(struct super_block *sb)
>  static inline int ext4_issue_discard(struct super_block *sb,
>  		ext4_group_t block_group, ext4_grpblk_t block, int count)
>  {
> -	int ret;
>  	ext4_fsblk_t discard_block;
>  
>  	discard_block = block + ext4_group_first_block_no(sb, block_group);
>  	trace_ext4_discard_blocks(sb,
>  			(unsigned long long) discard_block, count);
> -	ret = sb_issue_discard(sb, discard_block, count, GFP_NOFS, 0);
> -	if (ret == -EOPNOTSUPP) {
> -		ext4_warning(sb, "discard not supported, disabling");
> -		clear_opt(EXT4_SB(sb)->s_mount_opt, DISCARD);
> -	}
> -	return ret;
> +	return sb_issue_discard(sb, discard_block, count, GFP_NOFS, 0);
>  }
>  
>  /*
> @@ -2631,7 +2625,7 @@ static void release_blocks_on_commit(journal_t *journal, transaction_t *txn)
>  	struct super_block *sb = journal->j_private;
>  	struct ext4_buddy e4b;
>  	struct ext4_group_info *db;
> -	int err, count = 0, count2 = 0;
> +	int err, ret, count = 0, count2 = 0;
>  	struct ext4_free_data *entry;
>  	struct list_head *l, *ltmp;
>  
> @@ -2641,9 +2635,15 @@ static void release_blocks_on_commit(journal_t *journal, transaction_t *txn)
>  		mb_debug(1, "gonna free %u blocks in group %u (0x%p):",
>  			 entry->count, entry->group, entry);
>  
> -		if (test_opt(sb, DISCARD))
> -			ext4_issue_discard(sb, entry->group,
> +		if (test_opt(sb, DISCARD)) {
> +			ret = ext4_issue_discard(sb, entry->group,
>  					entry->start_blk, entry->count);
> +			if (unlikely(ret == -EOPNOTSUPP)) {
> +				ext4_warning(sb, "discard not supported, "
> +						 "disabling");
> +				clear_opt(EXT4_SB(sb)->s_mount_opt, DISCARD);
> +			}
> +		}
>  
>  		err = ext4_mb_load_buddy(sb, entry->group, &e4b);
>  		/* we expect to find existing buddy because it's pinned */
> @@ -4718,8 +4718,6 @@ static int ext4_trim_extent(struct super_block *sb, int start, int count,
>  	ext4_unlock_group(sb, group);
>  
>  	ret = ext4_issue_discard(sb, group, start, count);
> -	if (ret)
> -		ext4_std_error(sb, ret);
>  
>  	ext4_lock_group(sb, group);
>  	mb_free_blocks(NULL, e4b, start, ex.fe_len);
> 

Ping

  reply	other threads:[~2010-12-20 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 18:42 [PATCH] ext4: Remove warning message from ext4_issue_discard helper Lukas Czerner
2010-12-20 11:19 ` Lukas Czerner [this message]
2010-12-20 13:06 ` Ted 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.1012201218470.12772@dhcp-lab-213.englab.brq.redhat.com \
    --to=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).