public inbox for [email protected]
 help / color / mirror / Atom feed
From: Stefan Roesch <[email protected]>
To: Filipe Manana <[email protected]>
Cc: [email protected], [email protected],
	[email protected], [email protected],
	[email protected]
Subject: Re: [PATCH v2 08/12] btrfs: make lock_and_cleanup_extent_if_need nowait compatible
Date: Thu, 8 Sep 2022 11:38:53 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAL3q7H5QnvPNtNq-uvXBsFNT=URXU4pKDaUqZGrf3MPt7VgBSA@mail.gmail.com>



On 9/8/22 3:17 AM, Filipe Manana wrote:
> > 
> On Thu, Sep 8, 2022 at 1:26 AM Stefan Roesch <[email protected]> wrote:
>>
>> This adds the nowait parameter to lock_and_cleanup_extent_if_need(). If
>> the nowait parameter is specified we try to lock the extent in nowait
>> mode.
>>
>> Signed-off-by: Stefan Roesch <[email protected]>
>> ---
>>  fs/btrfs/file.c | 18 +++++++++++++++---
>>  1 file changed, 15 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
>> index a154a3cec44b..4e1745e585cb 100644
>> --- a/fs/btrfs/file.c
>> +++ b/fs/btrfs/file.c
>> @@ -1440,7 +1440,7 @@ static noinline int
>>  lock_and_cleanup_extent_if_need(struct btrfs_inode *inode, struct page **pages,
>>                                 size_t num_pages, loff_t pos,
>>                                 size_t write_bytes,
>> -                               u64 *lockstart, u64 *lockend,
>> +                               u64 *lockstart, u64 *lockend, bool nowait,
>>                                 struct extent_state **cached_state)
>>  {
>>         struct btrfs_fs_info *fs_info = inode->root->fs_info;
>> @@ -1455,8 +1455,20 @@ lock_and_cleanup_extent_if_need(struct btrfs_inode *inode, struct page **pages,
>>         if (start_pos < inode->vfs_inode.i_size) {
>>                 struct btrfs_ordered_extent *ordered;
>>
>> -               lock_extent_bits(&inode->io_tree, start_pos, last_pos,
>> +               if (nowait) {
>> +                       if (!try_lock_extent(&inode->io_tree, start_pos, last_pos)) {
>> +                               for (i = 0; i < num_pages; i++) {
>> +                                       unlock_page(pages[i]);
>> +                                       put_page(pages[i]);
> 
> Since this is a non-local array, I'd prefer if we also set pages[i] to NULL.
> That may help prevent hard to debug bugs in the future.
> 
> Thanks.
> 
> 

I set pages[i] to null in the next version of the patch series.

>> +                               }
>> +
>> +                               return -EAGAIN;
>> +                       }
>> +               } else {
>> +                       lock_extent_bits(&inode->io_tree, start_pos, last_pos,
>>                                 cached_state);
>> +               }
>> +
>>                 ordered = btrfs_lookup_ordered_range(inode, start_pos,
>>                                                      last_pos - start_pos + 1);
>>                 if (ordered &&
>> @@ -1755,7 +1767,7 @@ static noinline ssize_t btrfs_buffered_write(struct kiocb *iocb,
>>                 extents_locked = lock_and_cleanup_extent_if_need(
>>                                 BTRFS_I(inode), pages,
>>                                 num_pages, pos, write_bytes, &lockstart,
>> -                               &lockend, &cached_state);
>> +                               &lockend, false, &cached_state);
>>                 if (extents_locked < 0) {
>>                         if (extents_locked == -EAGAIN)
>>                                 goto again;
>> --
>> 2.30.2
>>

  reply	other threads:[~2022-09-08 18:39 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  0:26 [PATCH v2 00/12] io-uring/btrfs: support async buffered writes Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 01/12] mm: export balance_dirty_pages_ratelimited_flags() Stefan Roesch
2022-09-08 10:18   ` Filipe Manana
2022-09-08  0:26 ` [PATCH v2 02/12] btrfs: implement a nowait option for tree searches Stefan Roesch
2022-09-08 13:19   ` Josef Bacik
2022-09-08 18:05     ` Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 03/12] btrfs: make can_nocow_extent nowait compatible Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 04/12] btrfs: add the ability to use NO_FLUSH for data reservations Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 05/12] btrfs: add btrfs_try_lock_ordered_range Stefan Roesch
2022-09-08 10:18   ` Filipe Manana
2022-09-08 18:12     ` Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 06/12] btrfs: make btrfs_check_nocow_lock nowait compatible Stefan Roesch
2022-09-08 10:18   ` Filipe Manana
2022-09-08 18:23     ` Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 07/12] btrfs: make prepare_pages " Stefan Roesch
2022-09-08 10:17   ` Filipe Manana
2022-09-08 18:33     ` Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 08/12] btrfs: make lock_and_cleanup_extent_if_need " Stefan Roesch
2022-09-08 10:17   ` Filipe Manana
2022-09-08 18:38     ` Stefan Roesch [this message]
2022-09-08  0:26 ` [PATCH v2 09/12] btrfs: btrfs: plumb NOWAIT through the write path Stefan Roesch
2022-09-08 10:16   ` Filipe Manana
2022-09-08 18:44     ` Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 10/12] btrfs: make balance_dirty_pages nowait compatible Stefan Roesch
2022-09-08 10:16   ` Filipe Manana
2022-09-08 18:48     ` Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 11/12] btrfs: add assert to search functions Stefan Roesch
2022-09-08 10:15   ` Filipe Manana
2022-09-08 19:10     ` Stefan Roesch
2022-09-08  0:26 ` [PATCH v2 12/12] btrfs: enable nowait async buffered writes Stefan Roesch
2022-09-08 10:14   ` Filipe Manana
2022-09-08 19:14     ` Stefan Roesch
2022-09-08 10:14 ` [PATCH v2 00/12] io-uring/btrfs: support " Filipe Manana

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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