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
| ||
|
Message-ID: <Y7Xg19H39FqTwyEL@gmail.com> Date: Wed, 4 Jan 2023 21:25:59 +0100 From: Ingo Molnar <mingo@...nel.org> To: "Jason A. Donenfeld" <Jason@...c4.com> Cc: Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org, patches@...ts.linux.dev, tglx@...utronix.de, linux-crypto@...r.kernel.org, linux-api@...r.kernel.org, x86@...nel.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Adhemerval Zanella Netto <adhemerval.zanella@...aro.org>, Carlos O'Donell <carlos@...hat.com>, Florian Weimer <fweimer@...hat.com>, Arnd Bergmann <arnd@...db.de>, Jann Horn <jannh@...gle.com>, Christian Brauner <brauner@...nel.org> Subject: Re: [PATCH v14 1/7] x86: lib: Separate instruction decoder MMIO type from MMIO trace * Ingo Molnar <mingo@...nel.org> wrote: > > * Jason A. Donenfeld <Jason@...c4.com> wrote: > > > On Tue, Jan 3, 2023 at 6:29 PM Borislav Petkov <bp@...en8.de> wrote: > > > > > > On Tue, Jan 03, 2023 at 06:00:46PM +0100, Ingo Molnar wrote: > > > > > I guess you missed the conversation with Borislav yesterday about that. > > > > > He mentioned that I'd just take it through random.git when this whole > > > > > series goes in. > > > > > > > > Please base your tree off on tip:x86/asm then (or pull it in) - it only > > > > > > My idea was a lot simpler: avoid the tree inter-dependency by us acking this > > > patch so that it can go through the random.git tree. > > > > Indeed I would prefer this. > > > > Or... just put this in 6.2 because it's trivial anyway? Heck, even mark > > it as stable@ so make future backporting easier. Then it'll meet tip's > > urgent criteria. > > Yeah - that's sensible too, it does fix a header namespace bug - I've put > it into tip:x86/urgent. This namespace clash fix is now upstream as of 512dee0c00ad & later kernels. Thanks, Ingo
Powered by blists - more mailing lists