Re: [PATCH v7 09/26] x86/insn-eval: Add utility function to identify string instructions

2017-05-29 Thread Borislav Petkov
On Fri, May 05, 2017 at 11:17:07AM -0700, Ricardo Neri wrote: > String instructions are special because in protected mode, the linear > address is always obtained via the ES segment register in operands that > use the (E)DI register. ... and DS for rSI. If we're going to account for both

Re: [PATCH v7 08/26] x86/insn-eval: Add a utility function to get register offsets

2017-05-29 Thread Borislav Petkov
On Fri, May 05, 2017 at 11:17:06AM -0700, Ricardo Neri wrote: > The function get_reg_offset() returns the offset to the register the > argument specifies as indicated in an enumeration of type offset. Callers > of this function would need the definition of such enumeration. This is > not needed.

Re: [PATCH v7 07/26] x86/insn-eval: Do not BUG on invalid register type

2017-05-29 Thread Borislav Petkov
On Fri, May 05, 2017 at 11:17:05AM -0700, Ricardo Neri wrote: > We are not in a critical failure path. The invalid register type is caused > when trying to decode invalid instruction bytes from a user-space program. > Thus, simply print an error message. To prevent this warning from being > abused

_3дрaвствyйтe! Вaс uнтeрeсyют клueнтскue бaзы дaнныx?

2017-05-29 Thread lera.pelt2...@yandex.ru
_Зqравствyйте! Bас интересyют kлиентсkие 6азы qанных?

Re: [PATCH v7 05/26] x86/mpx: Do not use SIB.base if its value is 101b and ModRM.mod = 0

2017-05-29 Thread Borislav Petkov
On Fri, May 05, 2017 at 11:17:03AM -0700, Ricardo Neri wrote: > Section 2.2.1.2 of the Intel 64 and IA-32 Architectures Software > Developer's Manual volume 2A states that when a SIB byte is used and the > base of the SIB byte points is base = 101b and the mod part > of the ModRM byte is zero, the