linux-kernel - Re: [f2fs-dev] [PATCH V3 6/6] xfs: ignore discard return value

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251126103408.GC26228@lst.de>
Date: Wed, 26 Nov 2025 11:34:08 +0100
From: "hch@....de" <hch@....de>
To: Chaitanya Kulkarni <chaitanyak@...dia.com>
Cc: Yongpeng Yang <yangyongpeng.storage@...il.com>,
	Chaitanya Kulkarni <ckulkarnilinux@...il.com>,
	"axboe@...nel.dk" <axboe@...nel.dk>,
	"agk@...hat.com" <agk@...hat.com>,
	"snitzer@...nel.org" <snitzer@...nel.org>,
	"mpatocka@...hat.com" <mpatocka@...hat.com>,
	"song@...nel.org" <song@...nel.org>,
	"yukuai@...as.com" <yukuai@...as.com>, "hch@....de" <hch@....de>,
	"sagi@...mberg.me" <sagi@...mberg.me>,
	"jaegeuk@...nel.org" <jaegeuk@...nel.org>,
	"chao@...nel.org" <chao@...nel.org>,
	"cem@...nel.org" <cem@...nel.org>,
	"dm-devel@...ts.linux.dev" <dm-devel@...ts.linux.dev>,
	"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
	Johannes Thumshirn <johannes.thumshirn@....com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
	"linux-f2fs-devel@...ts.sourceforge.net" <linux-f2fs-devel@...ts.sourceforge.net>,
	"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
	"bpf@...r.kernel.org" <bpf@...r.kernel.org>,
	"linux-xfs@...r.kernel.org" <linux-xfs@...r.kernel.org>,
	Yongpeng Yang <yangyongpeng@...omi.com>
Subject: Re: [f2fs-dev] [PATCH V3 6/6] xfs: ignore discard return value

On Wed, Nov 26, 2025 at 08:07:21AM +0000, Chaitanya Kulkarni wrote:
> The retry for discard bio memory allocation is not desired I think,
> since it's only a hint to the controller.

Yes, it is.  The command is defined as a hint, but it's required for
a lot of workloads to work.  It's not just a speculative readahead.