From: Johannes Weiner <hannes@cmpxchg.org>
To: Jaswinder Singh Rajput <jaswinder@infradead.org>
Cc: Chris Mason <chris.mason@oracle.com>,
linux-btrfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: Remove useless condition
Date: Sun, 12 Sep 2010 14:29:55 +0200 [thread overview]
Message-ID: <20100912122955.GA28839@cmpxchg.org> (raw)
In-Reply-To: <1284289340.2650.2.camel@ht.satnam>
On Sun, Sep 12, 2010 at 04:32:20PM +0530, Jaswinder Singh Rajput wrote:
>
> if (ret) is useless as it will be never NULL as in previous statement
> we are setting ret = prev for !ret
If there is no match and no extent below the given file offset, `prev'
will be NULL as well, no?
So the check is not useless, it prevents throwing out a cached success
in case of a lookup failure.
> Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> Cc: Chris Mason <chris.mason@oracle.com>
> ---
> fs/btrfs/ordered-data.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/fs/btrfs/ordered-data.c b/fs/btrfs/ordered-data.c
> index e56c72b..7b04008 100644
> --- a/fs/btrfs/ordered-data.c
> +++ b/fs/btrfs/ordered-data.c
> @@ -154,8 +154,7 @@ static inline struct rb_node *tree_search(struct btrfs_ordered_inode_tree *tree,
> ret = __tree_search(root, file_offset, &prev);
> if (!ret)
> ret = prev;
> - if (ret)
> - tree->last = ret;
> + tree->last = ret;
> return ret;
> }
>
> --
> 1.7.2.2
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2010-09-12 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 11:02 [PATCH] Btrfs: Remove useless condition Jaswinder Singh Rajput
2010-09-12 12:29 ` Johannes Weiner [this message]
2010-09-12 13:56 ` Jaswinder Singh Rajput
2010-09-12 17:28 ` Mike Fedyk
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=20100912122955.GA28839@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=chris.mason@oracle.com \
--cc=jaswinder@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).