linux-kernel - Re: [Linux-nvdimm] [GIT PULL] PMEM driver for v4.1

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: <20150525181654.GE2729@linux.intel.com>
Date:	Mon, 25 May 2015 14:16:54 -0400
From:	Matthew Wilcox <willy@...ux.intel.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-nvdimm@...ts.01.org, linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@....de>
Subject: Re: [Linux-nvdimm] [GIT PULL] PMEM driver for v4.1

On Mon, Apr 13, 2015 at 11:33:09AM +0200, Ingo Molnar wrote:
> Please pull the latest x86-pmem-for-linus git tree from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pmem-for-linus
> 
>    # HEAD: 4c1eaa2344fb26bb5e936fb4d8ee307343ea0089 drivers/block/pmem: Fix 32-bit build warning in pmem_alloc()
> 
> This is the initial support for the pmem block device driver: 
> persistent non-volatile memory space mapped into the system's physical 
> memory space as large physical memory regions.

Ingo, this sucks.  You collapsed all of the separate patches into a
single "add new driver" patch, which makes it impossible to bisect which
of the recent changes broke xfstests.  Please don't do this again.

> ------------------>
> Christoph Hellwig (1):
>       x86/mm: Add support for the non-standard protected e820 type
> 
> Ingo Molnar (1):
>       drivers/block/pmem: Fix 32-bit build warning in pmem_alloc()
> 
> Ross Zwisler (1):
>       drivers/block/pmem: Add a driver for persistent memory

--
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/