All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 3/3] btrfs: remove processed_extent infrastructure
Date: Mon, 29 May 2023 22:43:01 -0700	[thread overview]
Message-ID: <ZHWM5U754Na8KyCi@infradead.org> (raw)
In-Reply-To: <5b3edb0ed26aa790fa92d0319739adfd71b3b2f5.1685411033.git.wqu@suse.com>

I recently posted an equivalent patch:

https://www.spinics.net/lists/linux-btrfs/msg134188.html

but it turns out this actually breaks with compression enabled, where
due to the ompression we can get gaps in the logical addresses.  IIRC
you had to do an auto run with -o compress to catch it.


  reply	other threads:[~2023-05-30  5:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  1:45 [PATCH v2 0/3] btrfs: small cleanups mostly for subpage cases Qu Wenruo
2023-05-30  1:45 ` [PATCH v2 1/3] btrfs: make alloc_extent_buffer() handle previously uptodate range more efficient for subpage Qu Wenruo
2023-05-30  5:41   ` Christoph Hellwig
2023-05-30  1:45 ` [PATCH v2 2/3] btrfs: use the same @uptodate variable for end_bio_extent_readpage() Qu Wenruo
2023-05-30  5:41   ` Christoph Hellwig
2023-05-30  6:06   ` Anand Jain
2023-05-30  1:45 ` [PATCH v2 3/3] btrfs: remove processed_extent infrastructure Qu Wenruo
2023-05-30  5:43   ` Christoph Hellwig [this message]
2023-05-30  6:19     ` Qu Wenruo
2023-05-30 23:35       ` Qu Wenruo
2023-05-31  4:33         ` Christoph Hellwig
2023-05-30 12:48 ` [PATCH v2 0/3] btrfs: small cleanups mostly for subpage cases David Sterba

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=ZHWM5U754Na8KyCi@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.