Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Josef Bacik <josef@toxicpanda.com>,
	linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: Update btrfs/215
Date: Tue, 8 Dec 2020 10:15:44 +0200	[thread overview]
Message-ID: <935d9d3b-4cd1-d1a7-d911-424ee0ccbecc@suse.com> (raw)
In-Reply-To: <1c23bd14-3c30-603f-0014-a1aeeb8ef8ab@toxicpanda.com>



On 7.12.20 г. 18:36 ч., Josef Bacik wrote:
> On 12/7/20 4:23 AM, Nikolay Borisov wrote:
>> This patch updates btrfs/215 to work with latest upstream kernel. That's
>> required since commit 324bcf54c449 ("mm: use limited read-ahead to
>> satisfy read")
>> changed readahead logic to always issue a read even if the RA pages are
>> set to 0. This results in 1 extra io being issued so the counts in the
>> test should be incremented by 1. Also use the opportunity to update the
>> commit reference since it's been merged in the upstream kernel.
>>
>> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
>> ---
>> V2:
>>   * Updated comment above buffered read issue command to better
>> describe why 2
>>   failures are expected.
> 
> Do we want to just test for non-zero, since the original problem was
> that we weren't getting any error stats at all?  Then we don't have to
> worry about new edge cases in the future.  Thanks,


I'da rather have precise numbers so that when something changes and the
test blips red I can go and do a targeted investigation. Esp. with the
subapge rework pending.

> 
> Josef
> 

      reply	other threads:[~2020-12-08  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07  9:23 [PATCH v2] btrfs: Update btrfs/215 Nikolay Borisov
2020-12-07 16:36 ` Josef Bacik
2020-12-08  8:15   ` Nikolay Borisov [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=935d9d3b-4cd1-d1a7-d911-424ee0ccbecc@suse.com \
    --to=nborisov@suse.com \
    --cc=fstests@vger.kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@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