From: Christoph Hellwig <hch@lst.de>
To: John Garry <john.g.garry@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 1/2] block: blocking mempool_alloc doesn't fail
Date: Mon, 3 Nov 2025 12:52:06 +0100 [thread overview]
Message-ID: <20251103115206.GA15538@lst.de> (raw)
In-Reply-To: <65386bdd-6cd9-44ff-9c43-2e9343f6ced9@oracle.com>
On Mon, Nov 03, 2025 at 11:26:56AM +0000, John Garry wrote:
> Is the original error handling code correct?
Does it matter given that it was never called and is removed now? :)
next prev parent reply other threads:[~2025-11-03 11:52 UTC|newest]
Thread overview: 21+ 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 [this message]
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
2025-11-05 19:46 ` Christoph Hellwig
2025-11-05 19:48 ` Jens Axboe
2025-11-05 15:06 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-10-30 14:44 make block layer auto-PI deadlock safe v2 Christoph Hellwig
2025-10-30 14:44 ` [PATCH 1/2] block: blocking mempool_alloc doesn't fail Christoph Hellwig
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=20251103115206.GA15538@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=john.g.garry@oracle.com \
--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.