linux-kernel - Re: [PATCH 0/3] mm/powerpc: enabling memory soft dirty tracking

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: <20151016141129.8b014c6d882c475fafe577a9@linux-foundation.org>
Date:	Fri, 16 Oct 2015 14:11:29 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Laurent Dufour <ldufour@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	xemul@...allels.com, linuxppc-dev@...ts.ozlabs.org,
	mpe@...erman.id.au, benh@...nel.crashing.org,
	aneesh.kumar@...ux.vnet.ibm.com, paulus@...ba.org, criu@...nvz.org
Subject: Re: [PATCH 0/3] mm/powerpc: enabling memory soft dirty tracking

On Fri, 16 Oct 2015 14:07:05 +0200 Laurent Dufour <ldufour@...ux.vnet.ibm.com> wrote:

> This series is enabling the software memory dirty tracking in the
> kernel for powerpc.  This is the follow up of the commit 0f8975ec4db2
> ("mm: soft-dirty bits for user memory changes tracking") which
> introduced this feature in the mm code.
> 
> The first patch is fixing an issue in the code clearing the soft dirty
> bit.  The PTE were not cleared before being modified, leading to hang
> on ppc64.
> 
> The second patch is fixing a build issue when the transparent huge
> page is not enabled.
> 
> The third patch is introducing the soft dirty tracking in the powerpc
> architecture code. 

I grabbed these patches, but they're more a ppc thing than a core
kernel thing.  I can merge them into 4.3 with suitable acks or drop
them if they turn up in the powerpc tree.  Or something else?
--
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/