From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id CF9382020D334 for ; Mon, 19 Aug 2019 19:27:45 -0700 (PDT) Date: Tue, 20 Aug 2019 04:26:19 +0200 From: Christoph Hellwig Subject: Re: [PATCH 1/4] resource: add a not device managed request_free_mem_region variant Message-ID: <20190820022619.GA23225@lst.de> References: <20190818090557.17853-1-hch@lst.de> <20190818090557.17853-2-hch@lst.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dan Williams Cc: linux-nvdimm , Linux Kernel Mailing List , Bharata B Rao , Linux MM , Jason Gunthorpe , Andrew Morton , Christoph Hellwig List-ID: On Mon, Aug 19, 2019 at 06:28:30PM -0700, Dan Williams wrote: > > Previously we would loudly crash if someone passed NULL to > devm_request_free_mem_region(), but now it will silently work and the > result will leak. Perhaps this wants a: We'd still instantly crash due to the dev_name dereference, right? _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm