linux-kernel - Re: [PATCH v3 05/11] x86/tracing: fix compat syscall handling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <413d180f-2620-7471-8fa9-f576e3a457b2@imgtec.com>
Date:   Thu, 13 Oct 2016 08:32:38 +0200
From:   Marcin Nowakowski <marcin.nowakowski@...tec.com>
To:     Thomas Gleixner <tglx@...utronix.de>
CC:     <linux-kernel@...r.kernel.org>, <linux-api@...r.kernel.org>,
        <luto@...capital.net>, <rostedt@...dmis.org>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, <x86@...nel.org>
Subject: Re: [PATCH v3 05/11] x86/tracing: fix compat syscall handling

On 12.10.2016 15:53, Thomas Gleixner wrote:
> On Tue, 11 Oct 2016, Marcin Nowakowski wrote:
>> -/*
>> - * Because ia32 syscalls do not map to x86_64 syscall numbers
>> - * this screws up the trace output when tracing a ia32 task.
>> - * Instead of reporting bogus syscalls, just do not trace them.
>> - *
>> - * If the user really wants these, then they should use the
>> - * raw syscall tracepoints with filtering.
>
> Why aren't you moving this information to the new place? It's valuable.

Well - much of this information is no longer true as with these fixes 
tracing can work properly, but I can keep a note clarifying that the 
numbers are mapped differently and why arch_syscall_addr() needs the 
sort of handling it does.

Marcin