From: David Sterba <dsterba@suse.cz>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: linux-btrfs@vger.kernel.org, Qu Wenruo <wqu@suse.com>
Subject: Re: [PATCH] btrfs: Correct try_lock_extent() usage in read_extent_buffer_subpage()
Date: Fri, 23 Apr 2021 12:43:20 +0200 [thread overview]
Message-ID: <20210423104320.GD7604@twin.jikos.cz> (raw)
In-Reply-To: <20210408124025.ljsgund6jfc5c55y@fiona>
On Thu, Apr 08, 2021 at 07:40:25AM -0500, Goldwyn Rodrigues wrote:
> try_lock_extent() returns 1 on success or 0 for failure and not an error
> code. If try_lock_extent() fails, read_extent_buffer_subpage() returns
> zero indicating subpage extent read success.
>
> Return EAGAIN/EWOULDBLOCK if try_lock_extent() fails in locking the
> extent.
>
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
Added to misc-next, thanks.
prev parent reply other threads:[~2021-04-23 10:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 12:40 [PATCH] btrfs: Correct try_lock_extent() usage in read_extent_buffer_subpage() Goldwyn Rodrigues
2021-04-08 12:45 ` Qu Wenruo
2021-04-08 18:05 ` Josef Bacik
2021-04-23 10:43 ` David Sterba [this message]
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=20210423104320.GD7604@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.de \
--cc=wqu@suse.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;
as well as URLs for NNTP newsgroup(s).