From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: "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 08:03:57 -0700 [thread overview]
Message-ID: <a18092a0-da9c-430b-80a4-5951501f94ef@kernel.dk> (raw)
In-Reply-To: <20251105132345.GA19731@lst.de>
On 11/5/25 6:23 AM, Christoph Hellwig wrote:
>> 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)
But why not generate it against the 6.19 tree then? As-is, I have to
first resolve the conflict in that tree, then resolve it again when
merging to for-next. Not a huge issue, just don't quite follow the logic
behind generating it against block-6.18.
--
Jens Axboe
next prev parent reply other threads:[~2025-11-05 15:04 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
2025-11-05 15:03 ` Jens Axboe [this message]
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=a18092a0-da9c-430b-80a4-5951501f94ef@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox