From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752430AbeEOVnm (ORCPT ); Tue, 15 May 2018 17:43:42 -0400 Received: from mail-wr0-f169.google.com ([209.85.128.169]:40214 "EHLO mail-wr0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752383AbeEOVnl (ORCPT ); Tue, 15 May 2018 17:43:41 -0400 X-Google-Smtp-Source: AB8JxZptKNEo6kFFscACuZ5Dndgeoe/1ZNK1I6q7Il38EfmSUxfD+4bYwcLrH5hhXmcWgh6K5WbIJg== Date: Wed, 16 May 2018 00:43:37 +0300 From: Alexey Dobriyan To: "Anvin, H Peter" Cc: "Ye, Xiaolong" , Ingo Molnar , Thomas Gleixner , Andy Lutomirski , Borislav Petkov , Brian Gerst , Denys Vlasenko , Josh Poimboeuf , Linus Torvalds , Peter Zijlstra , LKML , "H. Peter Anvin" , "tipbuild@zytor.com" , "lkp@01.org" Subject: Re: [lkp-robot] [x86/asm] 51bad67ffb: int3:#[##] Message-ID: <20180515214337.GA18021@avx2> References: <20180515080033.GA7714@yexl-desktop> <20180515210757.GA12225@avx2> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 15, 2018 at 09:25:53PM +0000, Anvin, H Peter wrote: > Why is that a problem? > Code: 00 00 00 eb e6 cc cc cc cc cc cc cc cc cc cc cc cc cc fa 8d b6 00 00 00 00 e8 5d e8 8f ff 8b 44 24 34 83 e0 03 83 f8 03 72 28 cc <cc> cc cc cc cc cc cc fa 8d b6 00 00 00 00 e8 3d e8 8f ff 89 e0 > > EIP: ret_from_intr+0xd/0x14 SS:ESP: 0068:8603bfb4 > > INT3 slipped through M586 => X86_ALIGNMENT_16 :-\ I could make the patch x86_64 only, but! It crashed into the middle of the padding. 796ef8fc : 796ef8fc: 8b 44 24 34 mov eax,DWORD PTR [esp+0x34] 796ef900: 83 e0 03 and eax,0x3 796ef903: 83 f8 03 cmp eax,0x3 796ef906: 72 28 jb 796ef930 796ef908: cc int3 796ef909: cc <========> int3 796ef90a: cc int3 796ef90b: cc int3 796ef90c: cc int3 796ef90d: cc int3 796ef90e: cc int3 796ef90f: cc int3 From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5710844348805346853==" MIME-Version: 1.0 From: Alexey Dobriyan To: lkp@lists.01.org Subject: Re: [lkp-robot] [x86/asm] 51bad67ffb: int3:#[##] Date: Wed, 16 May 2018 00:43:37 +0300 Message-ID: <20180515214337.GA18021@avx2> In-Reply-To: List-Id: --===============5710844348805346853== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, May 15, 2018 at 09:25:53PM +0000, Anvin, H Peter wrote: > Why is that a problem? > Code: 00 00 00 eb e6 cc cc cc cc cc cc cc cc cc cc cc cc cc fa 8d b6 00 0= 0 00 00 e8 5d e8 8f ff 8b 44 24 34 83 e0 03 83 f8 03 72 28 cc <cc> cc= cc cc cc cc cc fa 8d b6 00 00 00 00 e8 3d e8 8f ff 89 e0 > = > EIP: ret_from_intr+0xd/0x14 SS:ESP: 0068:8603bfb4 > = > INT3 slipped through M586 =3D> X86_ALIGNMENT_16 :-\ I could make the patch x86_64 only, but! It crashed into the middle of the padding. 796ef8fc : 796ef8fc: 8b 44 24 34 mov eax,DWORD PTR [esp+0x34] 796ef900: 83 e0 03 and eax,0x3 796ef903: 83 f8 03 cmp eax,0x3 796ef906: 72 28 jb 796ef930 796ef908: cc int3 796ef909: cc <=3D=3D=3D=3D=3D=3D=3D=3D> int3 796ef90a: cc int3 796ef90b: cc int3 796ef90c: cc int3 796ef90d: cc int3 796ef90e: cc int3 796ef90f: cc int3 --===============5710844348805346853==--