All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-block@vger.kernel.org
Subject: Re: make block layer auto-PI deadlock safe v3
Date: Wed, 5 Nov 2025 14:23:45 +0100	[thread overview]
Message-ID: <20251105132345.GA19731@lst.de> (raw)
In-Reply-To: <afe10b17-245b-4b21-81ee-ff5589a7ca47@kernel.dk>

On Tue, Nov 04, 2025 at 12:47:09PM -0700, Jens Axboe wrote:
> > Fix this by adding a mempool, and capping the maximum I/O size on PI
> > capable devices to not exceed the allocation size of the mempool.
> > 
> > This is against the block-6.18 branch as it has a contextual dependency
> > on the PI fix merged there yesterday.
> 
> Yesterday? Guessing this got copy/pasted from the v1 posting, as it must
> be this one:

Yesterday as of the first post of the series, I should have updated this,
sorry.

> 
> commit 4c8cf6bd28d6fea23819f082ddc8063fd6fa963a (tag: block-6.18-20251023)
> Author: Christoph Hellwig <hch@lst.de>
> Date:   Wed Oct 22 10:33:31 2025 +0200
> 
>     block: require LBA dma_alignment when using PI
> 
> which is a bit longer ago.
> 
> But why? Surely this is 6.19 material?

This is 6.19 material.  That's just a heads up that you need a merge
(or rebase which I was hoping for as of the first round, but it's probably
too late now)


  reply	other threads:[~2025-11-05 13:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 10:16 make block layer auto-PI deadlock safe v3 Christoph Hellwig
2025-11-03 10:16 ` [PATCH 1/2] block: blocking mempool_alloc doesn't fail Christoph Hellwig
2025-11-03 11:16   ` Kanchan Joshi
2025-11-03 11:26   ` John Garry
2025-11-03 11:52     ` Christoph Hellwig
2025-11-03 13:20   ` Anuj gupta
2025-11-03 13:28   ` Johannes Thumshirn
2025-11-03 10:16 ` [PATCH 2/2] block: make bio auto-integrity deadlock safe Christoph Hellwig
2025-11-03 11:15   ` Kanchan Joshi
2025-11-03 13:20   ` Anuj gupta
2025-11-03 13:40   ` Johannes Thumshirn
2025-11-03 13:45     ` hch
2025-11-03 13:47       ` Johannes Thumshirn
2025-11-03 13:49         ` hch
2025-11-04 19:47 ` make block layer auto-PI deadlock safe v3 Jens Axboe
2025-11-05 13:23   ` Christoph Hellwig [this message]
2025-11-05 15:03     ` Jens Axboe
2025-11-05 19:46       ` Christoph Hellwig
2025-11-05 19:48         ` Jens Axboe
2025-11-05 15:06 ` Jens Axboe

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=20251105132345.GA19731@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=martin.petersen@oracle.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.