[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <mhng-3d8b7678-3ebc-4665-8b58-94b44be0fd7c@palmer-ri-x1c9a>
Date: Thu, 10 Aug 2023 20:34:24 -0700 (PDT)
From: Palmer Dabbelt <palmer@...osinc.com>
To: keescook@...omium.org
CC: naresh.kamboju@...aro.org, stable@...r.kernel.org,
lkft-triage@...ts.linaro.org, Greg KH <gregkh@...uxfoundation.org>,
sashal@...nel.org, anders.roxell@...aro.org,
linux-hardening@...r.kernel.org
Subject: Re: stable-rc: 6.1: gcc-plugins: Reorganize gimple includes for GCC 13
On Thu, 10 Aug 2023 20:30:52 PDT (-0700), keescook@...omium.org wrote:
> On Fri, Aug 11, 2023 at 08:47:53AM +0530, Naresh Kamboju wrote:
>> > > # first fixed commit: [e6a71160cc145e18ab45195abf89884112e02dfb]
>> > > gcc-plugins: Reorganize gimple includes for GCC 13
>> [...]
>>
>> > Commit e6a71160cc14 ("gcc-plugins: Reorganize gimple includes
>> > for GCC 13") was added in v6.2.
>>
>> This commit is needed.
>>
>> >
>> > I think you're saying you need it backported to the v6.1 stable tree?
>> > ("First bad commit" is really the first good commit?)
>>
>> First good commit.
>> We need to backport this patch for linux.6.1.y
>
> Okay! Thanks. :) Yeah, this could probably go to all the stable kernels,
> if someone wants to build with GCC 13 on older kernels.
I'm also sligtly lost in the bug report, but IIRC the GCC include
changes were really a GCC version issue not a kernel version issue. In
other words, any kernel would be impacted if it's built with the newer
GCC so this should be backported aggressively.
So
Acked-by: Palmer Dabbelt <palmer@...osinc.com>
Thanks!
Powered by blists - more mailing lists