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: <1462829283.3149.7.camel@intel.com>
Date:	Mon, 9 May 2016 21:28:06 +0000
From:	"Verma, Vishal L" <vishal.l.verma@...el.com>
To:	"jack@...e.cz" <jack@...e.cz>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
CC:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: Re: [RFC v3] [PATCH 0/18] DAX page fault locking

On Mon, 2016-04-18 at 23:35 +0200, Jan Kara wrote:
> <>

Hi Jan,

I've noticed that patches 1 through 12 of your series are relatively
independent, and are probably more stable than the remaining part of
the series that actually changes locking.

My dax error handling series also depends on the patches that change
zeroing in DAX (patches 5, 6, 9).

To allow the error handling stuff to move faster, can we split these
into two patchsets?

I was hoping to send the dax error handling series through the nvdimm
tree, and if you'd like, I can also prepend your patches 1-12 with my
series.

Let me know your preference.

Thanks,
	-Vishal

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ