public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: David Sterba <dsterba@suse.cz>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
	Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>,
	Damien Le Moal <damien.lemoal@wdc.com>,
	linux-block@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: fix a few zoned append issues v2 (now with Ccs)
Date: Wed, 4 Dec 2024 01:17:18 +0100	[thread overview]
Message-ID: <20241204001718.GA22411@lst.de> (raw)
In-Reply-To: <20241203170120.GE31418@twin.jikos.cz>

On Tue, Dec 03, 2024 at 06:01:20PM +0100, David Sterba wrote:
> On Fri, Nov 08, 2024 at 03:48:57PM +0100, Christoph Hellwig wrote:
> > On Mon, Nov 04, 2024 at 07:26:28AM +0100, Christoph Hellwig wrote:
> > > Hi Jens, hi Damien, hi btrfs maintainers,
> > 
> > How should we proceed with this?  Should Jens just pick up the block
> > bits and the btrfs maintainers pick up the btrfs once they are
> > ready and the block bits made it upstream?
> 
> The block layer patches are now in master, I'm adding the remaining
> patches to btrfs for-next.

Thanks.  I wanted to resend them, but my baseline testing still showed
crashes in generic/475 so I was looking into an expunge config to
check if there are no regressions first (there really shouldn't, but
I wanted to double check).


  reply	other threads:[~2024-12-04  0:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  6:26 fix a few zoned append issues v2 (now with Ccs) Christoph Hellwig
2024-11-04  6:26 ` [PATCH 1/5] block: take chunk_sectors into account in bio_split_write_zeroes Christoph Hellwig
2024-11-07 12:04   ` Damien Le Moal
2024-11-11 16:08   ` (subset) " Jens Axboe
2024-11-04  6:26 ` [PATCH 2/5] block: fix bio_split_rw_at to take zone_write_granularity into account Christoph Hellwig
2024-11-07 12:05   ` Damien Le Moal
2024-11-08  7:07   ` Johannes Thumshirn
2024-11-04  6:26 ` [PATCH 3/5] block: lift bio_is_zone_append to bio.h Christoph Hellwig
2024-11-08  7:08   ` Johannes Thumshirn
2024-11-04  6:26 ` [PATCH 4/5] btrfs: use bio_is_zone_append in the completion handler Christoph Hellwig
2024-11-08  7:08   ` Johannes Thumshirn
2024-11-04  6:26 ` [PATCH 5/5] btrfs: split bios to the fs sector size boundary Christoph Hellwig
2024-11-08  7:09   ` Johannes Thumshirn
2024-11-08 14:48 ` fix a few zoned append issues v2 (now with Ccs) Christoph Hellwig
2024-11-08 15:03   ` David Sterba
2024-12-03 17:01   ` David Sterba
2024-12-04  0:17     ` Christoph Hellwig [this message]
2024-12-04  6:13       ` Qu Wenruo

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=20241204001718.GA22411@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=clm@fb.com \
    --cc=damien.lemoal@wdc.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --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