On Tue, Aug 9, 2011 at 12:57 PM, H. Peter Anvin <h...@zytor.com> wrote:
> On 08/09/2011 10:22 AM, Andrew Lutomirski wrote:I'm far from an expert in exploit writing, but I suspect it's
>> In any case, my patch fixes DynamoRIO but not pin. Pin dies with:
>> [ 4988.945491] test_vsyscall emulated vsyscall from bogus
>> and I don't know what's going on. I suspect that the tracer assumes
>> x86 maintainers: I can think of a few choices:
>> 1. Stick a ret instruction in the vsyscall page. Downside: now
> How much worse is a ret instruction over the INT instructions that
sometimes an additional challenge to make sure that esi and edi are
valid pointers before jumping into the vsyscall. That's why I added
the code that turns EFAULT into SIGSEGV.
>> 3. Apply my patch and assume that the number of users that would
> Since pin is going to have to be fixed anyway to run on 3.x, it seems
> Now, the multimodal patch seems reasonable, too.
> I think to some extent there are no actually good solutions here, just
I have a rather minimal vm that actually works with vsyscall=none. If
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.