[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHk-=wgQvNhB+7nwUkWs8jkh8qbd0nipotYhhghFSVBNNoagcQ@mail.gmail.com>
Date: Wed, 20 Dec 2023 21:38:51 -0800
From: Linus Torvalds <torvalds@...uxfoundation.org>
To: Sami Tolvanen <samitolvanen@...gle.com>
Cc: Andrew Cooper <andrew.cooper3@...rix.com>, Borislav Petkov <bp@...en8.de>,
kernel test robot <oliver.sang@...el.com>, Thomas Gleixner <tglx@...utronix.de>, oe-lkp@...ts.linux.dev,
lkp@...el.com, linux-kernel@...r.kernel.org,
Dave Hansen <dave.hansen@...ux.intel.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>, xen-devel@...ts.xenproject.org
Subject: Re: [linus:master] [x86/entry] be5341eb0d: WARNING:CPU:#PID:#at_int80_emulation
On Wed, 20 Dec 2023 at 15:40, Sami Tolvanen <samitolvanen@...gle.com> wrote:
>
> I tested the patch with the 0-day bot reproducer and it does fix the
> warning. My usual arm64 and riscv configs also seem to build and boot
> just fine.
Thanks. I've been running it on my machine too, and still don't see
anything wrong with it..
I suspect all sane people are already on xmas break, which explains
why people are being quiet. They _should_ be.
But since I'm not in that sane group, I decided to just bypass the
normal channels and apply it directly.
It really isn't all that critical, since I don't expect anybody to
actually disable the posix timer subsystem: I think the config
variable came out of the kernel minimization project, and it's
probably much more likely that people turn off CFI (particularly since
you afaik still need to build with clang to get it) than that they'd
turn off the posix timer support.
But I think it's a worthy cleanup of some messy system call macros, so
I wanted to put this behind us whether it truly matters or not.
Linus
Powered by blists - more mailing lists