[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240323103827.GAZf6xI94u8F9LGBIL@fat_crate.local>
Date: Sat, 23 Mar 2024 11:38:27 +0100
From: Borislav Petkov <bp@...en8.de>
To: Kees Cook <keescook@...omium.org>
Cc: tglx@...utronix.de, Guixiong Wei <weiguixiong@...edance.com>,
jgross@...e.com, mingo@...hat.com, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, peterz@...radead.org,
gregkh@...uxfoundation.org, tony.luck@...el.com,
adobriyan@...il.com, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org
Subject: Re: [PATCH] x86, relocs: Ignore relocations in .notes section on
walk_relocs
On Fri, Mar 22, 2024 at 04:40:11PM -0700, Kees Cook wrote:
> The earlier patch, commit aaa8736370db ("x86, relocs: Ignore relocations
> in .notes section"), landed via my tree. It was sent out on Feb 22nd
> (v1[1]) and got a suggestion from HPA and a Review from Juergen Gross.
> I sent v2 Feb 27th[2] and it sat ignored for two weeks.
s/ignored for two weeks/missed in the avalance of patches/
> Since it was a 10 year old kernel address exposure, I sent it to Linus
> on Mar 12th[3].
So is there some unwritten understanding somewhere which says that you
should take tip patches through your tree?
Maybe I've missed it.
If there isn't, should we agree on something?
Because there clearly is a need for clarification here...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists