[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251126103700.GA28056@lst.de>
Date: Wed, 26 Nov 2025 11:37:00 +0100
From: Christoph Hellwig <hch@....de>
To: Yongpeng Yang <yangyongpeng.storage@...il.com>
Cc: Chaitanya Kulkarni <ckulkarnilinux@...il.com>, axboe@...nel.dk,
agk@...hat.com, snitzer@...nel.org, mpatocka@...hat.com,
song@...nel.org, yukuai@...as.com, hch@....de, sagi@...mberg.me,
kch@...dia.com, jaegeuk@...nel.org, chao@...nel.org, cem@...nel.org,
dm-devel@...ts.linux.dev, linux-raid@...r.kernel.org,
"Martin K . Petersen" <martin.petersen@...cle.com>,
Johannes Thumshirn <johannes.thumshirn@....com>,
linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org,
linux-f2fs-devel@...ts.sourceforge.net, linux-block@...r.kernel.org,
bpf@...r.kernel.org, linux-xfs@...r.kernel.org
Subject: Re: [f2fs-dev] [PATCH V3 4/6] nvmet: ignore discard return value
On Wed, Nov 26, 2025 at 06:14:32PM +0800, Yongpeng Yang wrote:
> We also need to check for memory allocation errors in
> __blkdev_issue_discard().
No, we still don't. What is so hard to grasp about mempool allocations
even after repeated explanations?
Powered by blists - more mailing lists