From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757285AbcH2Xzz (ORCPT ); Mon, 29 Aug 2016 19:55:55 -0400 Received: from mail-ua0-f175.google.com ([209.85.217.175]:33818 "EHLO mail-ua0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757165AbcH2Xzy (ORCPT ); Mon, 29 Aug 2016 19:55:54 -0400 MIME-Version: 1.0 In-Reply-To: <1472463007-6469-1-git-send-email-marcin.nowakowski@imgtec.com> References: <1472463007-6469-1-git-send-email-marcin.nowakowski@imgtec.com> From: Andy Lutomirski Date: Mon, 29 Aug 2016 16:55:27 -0700 Message-ID: Subject: Re: [PATCH 1/2] tracing/syscalls: allow multiple syscall numbers per syscall To: Marcin Nowakowski Cc: Linux API , linux-mips@vger.kernel.org, Ingo Molnar , Steven Rostedt , open list Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Aug 29, 2016 11:30 AM, "Marcin Nowakowski" wrote: > > Syscall metadata makes an assumption that only a single syscall number > corresponds to a given method. This is true for most archs, but > can break tracing otherwise. > > For MIPS platforms, depending on the choice of supported ABIs, up to 3 > system call numbers can correspond to the same call - depending on which > ABI the userspace app uses. MIPS isn't special here. x86 does the same thing. Why isn't this a problem on x86? Also, you seem to be partially reinventing AUDIT_ARCH here. Can you use that and integrate with syscall_get_arch()? --Andy