From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Paris <eparis@redhat.com>
Subject: Re: Benefit of 'arch' parameter for syscall rules
Date: Mon, 27 Sep 2010 13:10:40 -0400
Message-ID: <1285607440.2815.39.camel@localhost.localdomain>
References: <AANLkTimPovSxON1DnpMkPL6FEKOHAgSwmdLuLsCrz_s=@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <AANLkTimPovSxON1DnpMkPL6FEKOHAgSwmdLuLsCrz_s=@mail.gmail.com>
List-Unsubscribe: <https://www.redhat.com/mailman/options/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: Matt Rixon <rixon@ltceng.com>
Cc: Linux-audit@redhat.com
List-Id: linux-audit@redhat.com

On Mon, 2010-09-27 at 10:59 -0400, Matt Rixon wrote:
> Hi everyone,
> What is the benefit of using the 'arch' field parameter in a syscall
> rule?  Is it necessary?  

Yes, for some 'not so nice' (IMHO) reasons.  The syscall name you give
to -S is translated to a number and then matched exactly.  since syscall
#100 on x86_64 might not be the same as syscall #100 on x86_32 if you
don't supply a -F arch= you might end up getting chmod on 32bit and
socket on 64bit (I'm just making that up as an example)

I personally think userspace should handle that for you (instead of just
complaining lightly) if you don't enter -F arch= on a biarch system.

-Eric