linux-kernel - Re: [PATCH] nvme-pci: After the memory is released, the corresponding pointer needs to point to empty

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] [day] [month] [year] [list]

Message-ID: <20241022072913.GA12854@lst.de>
Date: Tue, 22 Oct 2024 09:29:13 +0200
From: Christoph Hellwig <hch@....de>
To: Liu Jing <liujing@...s.chinamobile.com>
Cc: kbusch@...nel.org, axboe@...nel.dk, hch@....de, sagi@...mberg.me,
	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nvme-pci: After the memory is released, the
 corresponding pointer needs to point to empty

On Tue, Oct 22, 2024 at 03:01:50AM +0800, Liu Jing wrote:
> The code frees memory pointed to by dev->queues. After freeing memory,
> dev->queues should be set to NULL to avoid dangling Pointers.

How claims that?  Clearing pointers clearly defeats redzoning in the
slab allocator so actually is counterproductive.