From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 21B43210D6903 for ; Thu, 5 Jul 2018 14:13:15 -0700 (PDT) Received: by mail-oi0-x242.google.com with SMTP id m2-v6so19545562oim.12 for ; Thu, 05 Jul 2018 14:13:15 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20180705201726.512-1-keith.busch@intel.com> References: <20180705201726.512-1-keith.busch@intel.com> From: Dan Williams Date: Thu, 5 Jul 2018 14:13:14 -0700 Message-ID: Subject: Re: [PATCHv2 1/2] libnvdimm: Use max contiguous area for namespace size 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: Keith Busch Cc: stable , linux-nvdimm List-ID: On Thu, Jul 5, 2018 at 1:17 PM, Keith Busch wrote: > This patch will find the max contiguous area to determine the largest > namespace size that can be created. If the requested size exceeds the > largest available, ENOSPC error will be returned. > > This fixes the allocation underrun error and wrong error return code > that have otherwise been observed as the following kernel warning: > > WARNING: CPU: PID: at drivers/nvdimm/namespace_devs.c:913 size_store > > Fixes: a1f3e4d6a0c3 ("libnvdimm, region: update nd_region_available_dpa() for multi-pmem support") > Cc: > Signed-off-by: Keith Busch > --- > v1 -> v2: > > Updated changelog to indicate the warning this patch fixes and copy > stable. > > Fixed code comments with the correct name of a function Looks good to me, applied to my for-4.18/libnvdimm tracking branch. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm