[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFw1MxjUKtrt-KyiNxmpuKUY273L5uy8ggzOFjBSYMwwog@mail.gmail.com>
Date: Tue, 15 May 2018 15:28:19 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Alexey Dobriyan <adobriyan@...il.com>,
Peter Anvin <h.peter.anvin@...el.com>,
kernel test robot <xiaolong.ye@...el.com>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Lutomirski <luto@...nel.org>,
Borislav Petkov <bp@...en8.de>,
Brian Gerst <brgerst@...il.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Anvin <hpa@...or.com>, tipbuild@...or.com,
LKP <lkp@...org>
Subject: Re: [lkp-robot] [x86/asm] 51bad67ffb: int3:#[##]
On Tue, May 15, 2018 at 3:22 PM Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> The padding isn't needed there, and the resume_userspace symbol is never
> used, so wouldn't this fix it?
This looks like the correct fix for this case, but are we sure there aren't
other cases where we have this same "fall through to an ENTRY" case?
Because we've definitely had that kind of code before too - sometimes
simply because we want profiles and oopses to show which "part" of the asm
we're faulting in (that could be the case here too).
Linus
Powered by blists - more mailing lists