From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 14/15] libnvdimm: support read-only btt backing devices Date: Mon, 22 Jun 2015 17:41:38 +0200 Message-ID: <20150622154138.GC7952@lst.de> References: <20150617235602.12943.24958.stgit@dwillia2-desk3.amr.corp.intel.com> <20150621101346.GF5915@lst.de> <20150621135406.GA9572@lst.de> <20150622063028.GA30434@lst.de> <20150622072844.GA31263@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from verein.lst.de ([213.95.11.211]:42692 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753774AbbFVPlk (ORCPT ); Mon, 22 Jun 2015 11:41:40 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Jeff Moyer Cc: Dan Williams , Jens Axboe , "linux-nvdimm@lists.01.org" , "linux-kernel@vger.kernel.org" , Linux ACPI , linux-fsdevel , Ingo Molnar On Mon, Jun 22, 2015 at 11:02:24AM -0400, Jeff Moyer wrote: > Agreed, we can't audit all code, and springing this potential data > corruptor on people seems irresponsible. How do "the people" know they'd have to use btt in the current setup without auditing their stack first? -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in