linux-kernel - Re: [GIT PULL] Couple more arm64 fixes for 4.19

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] [day] [month] [year] [list]

Message-ID: <20181013072823.GA27804@kroah.com>
Date:   Sat, 13 Oct 2018 09:28:23 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Will Deacon <will.deacon@....com>
Cc:     torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, catalin.marinas@....com
Subject: Re: [GIT PULL] Couple more arm64 fixes for 4.19

On Fri, Oct 12, 2018 at 04:46:29PM +0100, Will Deacon wrote:
> Hi Greg,
> 
> Please pull these two arm64 fixes for 4.19. One of them fixes a nasty
> WARN() that has started triggering because we assumed that memory
> reservations from firmware would always correspond to regions of the
> physical address space that we have mapped as memory. Unfortunately,
> some existing device-tree files break this assumption and we need to
> continue supporting them. The other fix addresses an issue where a
> CHAIN PMU event can be requested as a 32-bit counter via perf, which
> makes no sense in isolation since these events are intended to be used
> in conjunction with another event when creating a 64-bit counter.
> 
> This is summarised in the tag.

Now merged, thanks.

greg k-h