From: Chris Mason <chris.mason@oracle.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 09/18] btrfs: Fix return value of read_extent_buffer_pages() when lock page failed
Date: Tue, 30 Mar 2010 20:09:47 -0400 [thread overview]
Message-ID: <20100331000947.GS13190@think> (raw)
In-Reply-To: <4BAB5817.8020803@cn.fujitsu.com>
On Thu, Mar 25, 2010 at 08:33:27PM +0800, Miao Xie wrote:
> From: Zhao Lei <zhaolei@cn.fujitsu.com>
>
> read_extent_buffer_pages() should return error value instead of 0 when
> lock page failed, we fix this problem.
[ Thanks for all of these patches! ]
This isn't strictly an IO error, the caller has said they are not
willing to wait, so we don't wait. That's different from finding a page
where the IO had failed.
In general we ignore the errors until the caller is willing to wait for
the result.
-chris
>
> Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
> ---
> fs/btrfs/extent_io.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
> index bdfbfa6..3194c79 100644
> --- a/fs/btrfs/extent_io.c
> +++ b/fs/btrfs/extent_io.c
> @@ -3419,8 +3419,10 @@ int read_extent_buffer_pages(struct extent_io_tree *tree,
> for (i = start_i; i < num_pages; i++) {
> page = extent_buffer_page(eb, i);
> if (!wait) {
> - if (!trylock_page(page))
> + if (!trylock_page(page)) {
> + ret = -EIO;
> goto unlock_exit;
> + }
> } else {
> lock_page(page);
> }
> --
> 1.6.5.2
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-31 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 12:33 [PATCH 09/18] btrfs: Fix return value of read_extent_buffer_pages() when lock page failed Miao Xie
2010-03-31 0:09 ` Chris Mason [this message]
2010-03-31 4:04 ` Zhaolei
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=20100331000947.GS13190@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
/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