linux-ext4 - Re: [PATCH 0/4] ext4: DAX fixes

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]

Date:	Mon, 16 May 2016 08:13:50 -0700
From:	Dan Williams <dan.j.williams@...el.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	Jan Kara <jack@...e.cz>, linux-ext4 <linux-ext4@...r.kernel.org>,
	linux-nvdimm <linux-nvdimm@...1.01.org>,
	Vishal Verma <vishal.l.verma@...el.com>,
	Ross Zwisler <ross.zwisler@...ux.intel.com>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 0/4] ext4: DAX fixes

On Mon, May 16, 2016 at 8:08 AM, Theodore Ts'o <tytso@....edu> wrote:
> On Mon, May 16, 2016 at 04:26:16PM +0200, Jan Kara wrote:
>> 1) Just push patches as is and have ext4 dax broken between ext4 merge and
>> nvdimm merge.
>>
>> 2) Split out the one-line change from "dax: Remove dead zeroing code from
>> fault handlers" in __dax_fault() which fixes the behavior for ext4 and
>> merge it through ext4 tree. Merge the rest through nvdimm tree.
>
> I'm good either way, although I have a slight preference for (2).
> It's really tiny preference, though, so if you or Dan want to run the
> fix through the dax branch, that's fine too.

Would you fold the change and trigger a rebase or just apply it on
top?  If just applying on top then it seems the same exposure as
merging it intact through nvdimm.git.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html