linux-kernel - Re: [PATCH 4.9/4.14 BACKPORT 1/2] arm64: debug: Don't propagate UNKNOWN FAR into si

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

Message-ID: <20190405141649.GA7313@fuggles.cambridge.arm.com>
Date:   Fri, 5 Apr 2019 15:16:49 +0100
From:   Will Deacon <will.deacon@....com>
To:     Sasha Levin <sashal@...nel.org>
Cc:     gregkh@...uxfoundation.org, stable@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4.9/4.14 BACKPORT 1/2] arm64: debug: Don't propagate
 UNKNOWN FAR into si_code for debug signals

On Fri, Apr 05, 2019 at 02:15:21PM +0000, Sasha Levin wrote:
> Hi,
> 
> [This is an automated email]
> 
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: 4.14.+
> 
> The bot has tested the following trees: v5.0.6, v4.19.33, v4.14.110.
> 
> v4.19.33: Failed to apply! Possible dependencies:
>     Unable to calculate
> 
> v4.14.110: Build OK!
> 
> How should we proceed with this patch?

I did separate backports for the various stable trees, and annotated them
all accordingly in the subject and the @stable line. I think Greg has
already taken care of them.

Will