linux-kernel - Re: [PATCH 0/9] staging: Updates from the Android tree

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: <CALAqxLULe-ZfqRRkhxTg_BsCmfy6_TWsR3ck+Me84THyxHLjGg@mail.gmail.com>
Date:	Mon, 1 Feb 2016 13:28:46 -0800
From:	John Stultz <john.stultz@...aro.org>
To:	Laura Abbott <labbott@...hat.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Android Kernel Team <kernel-team@...roid.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	Sumit Semwal <sumit.semwal@...aro.org>
Subject: Re: [PATCH 0/9] staging: Updates from the Android tree

On Mon, Feb 1, 2016 at 1:10 PM, Laura Abbott <labbott@...hat.com> wrote:
> On 01/29/2016 10:07 PM, John Stultz wrote:
>>
>> In reviewing the experimental/android-4.4 tree from AOSP, I
>> realized there were a handful of patches to code in the
>> staging/android directory.
>>
>> So I wanted to send these along for review, so if there were
>> no objections they could be queued for 4.6.
>>
>> Let me know if there is any comments or feedback
>
>
> I'm not thrilled about the patches for the cache policy. It certainly
> fixes the problem for x86 but I'd rather see a more unified caching
> approach which would also abstract some of the cache flushing.

Fair enough.

Though I worry that keeping them out of mainline's staging makes it
more difficult to get a proper solution upstream, since it creates
more out of tree variants, which users may have subtle dependencies
on.  But that's more of a general worry then a specific concern here.

thanks
-john