linux-kernel - Re: [PATCH 3/3] pmem: Allow request_mem to fail, (CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM

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: <1424206333.12687.8.camel@theros.lm.intel.com>
Date:	Tue, 17 Feb 2015 13:52:13 -0700
From:	Ross Zwisler <ross.zwisler@...ux.intel.com>
To:	Boaz Harrosh <boaz@...xistor.com>
Cc:	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Roger C. Pao" <rcpao.enmotus@...il.com>,
	Dan Williams <dan.j.williams@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-nvdimm <linux-nvdimm@...ts.01.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH 3/3] pmem: Allow request_mem to fail,
 (CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET)

On Mon, 2015-02-16 at 13:24 +0200, Boaz Harrosh wrote:
> With old Kernels there was a bug in x86 where any unknown
> memory chip type would come up BUSY when calling
> request_mem_region_exclusive().
> 
> So for pmem to work with old Kernels and real NvDIMM chips
> we have a new Kconfig option CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET.
> 
> People have been running with hacked up pmem that will ignore
> the return code from request_mem_region_exclusive. So here it is
> official
> 
> Signed-off-by: Boaz Harrosh <boaz@...xistor.com>

I'm confused - I thought that this behavior was fixed by patch 1/3?
With that patch this memory reservation should not fail, correct?

If so, why do we need this patch?

> ---
>  drivers/block/Kconfig | 12 ++++++++++++
>  drivers/block/pmem.c  | 11 +++++++----
>  2 files changed, 19 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index 3b3200f..10879b8 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -430,6 +430,18 @@ config BLK_DEV_PMEM_USE_PAGES
>  	  to other devices in the system, then you must say "Yes" here.
>  	  If unsure leave as Yes.
>  
> +config BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET
> +	bool "Ignore the return code from request_mem_region_exclusive"
> +	depends on BLK_DEV_PMEM
> +	help
> +	  In Old Kernels type-12 Memory type which is used by NvDIMM
> +	  chips Comes out busy when calling request_mem_region_exclusive,
> +	  because of a bug.
> +	  If this option is set to "yes". The pmem will ignore the
> +	  failure, and continue as usual. If you have an old Kernel and
> +	  a real NvDIMM chip you must say yes here.
> +	  (Ignored if BLK_DEV_PMEM_USE_PAGES=y)
> +
>  config CDROM_PKTCDVD
>  	tristate "Packet writing on CD/DVD media"
>  	depends on !UML
> diff --git a/drivers/block/pmem.c b/drivers/block/pmem.c
> index 9eb7ffe..f84d033 100644
> --- a/drivers/block/pmem.c
> +++ b/drivers/block/pmem.c
> @@ -197,10 +197,12 @@ int pmem_mapmem(struct pmem_device *pmem)
>  
>  	res_mem = request_mem_region_exclusive(pmem->phys_addr, pmem->size,
>  					       "pmem");
> -	if (!res_mem) {
> +	if (unlikely(!res_mem)) {
>  		pr_warn("pmem: request_mem_region_exclusive phys=0x%llx size=0x%zx failed\n",
> -			   pmem->phys_addr, pmem->size);
> -		return -EINVAL;
> +			pmem->phys_addr, pmem->size);
> +#ifndef CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET
> +		return -EBUSY;
> +#endif
>  	}
>  
>  	pmem->virt_addr = ioremap_cache(pmem->phys_addr, pmem->size);
> @@ -211,7 +213,8 @@ int pmem_mapmem(struct pmem_device *pmem)
>  	return 0;
>  
>  out_release:
> -	release_mem_region(pmem->phys_addr, pmem->size);
> +	if (res_mem)
> +		release_mem_region(pmem->phys_addr, pmem->size);
>  	return err;
>  }
>  



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/