linux-kernel - Re: Clang patches for 4.9

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: <20190225144513.GA14055@kroah.com>
Date:   Mon, 25 Feb 2019 15:45:13 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Nathan Chancellor <natechancellor@...il.com>
Cc:     Sasha Levin <sashal@...nel.org>, stable@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: Clang patches for 4.9

On Sun, Feb 24, 2019 at 11:13:01PM -0700, Nathan Chancellor wrote:
> Hi Greg and Sasha,
> 
> Attached are three mbox files containing patches that bring the Clang
> backports that Nick did in 4.9.139 up to date with what is currently in
> 4.14 and mainline, as well as fix warnings that are present in the arm64
> and x86_64 defconfigs here and in AOSP (cuttlefish_defconfig). All of
> these warnings are fixed in 4.14 so there will be no regressions from
> upgrading.

Really?  I see a number of these only showing up in much newer kernels.
Specifically these patches:
  1f60652dd586 ("pinctrl: max77620: Use define directive for max77620_pinconf_param values")
  a0dd6773038f ("phy: tegra: remove redundant self assignment of 'map'")
  a9903f04e0a4 ("sched/sysctl: Fix attributes of some extern declarations")

from the "arm" mbox you provided.  Why shouldn't the above patches go
into 4.14.y and in some cases, also 4.19.y and 4.20.y?

thanks,

greg k-h