From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Question about max syscall number Date: Mon, 4 Aug 2008 15:46:11 -0400 Message-ID: <200808041546.12397.sgrubb@redhat.com> References: <001401c8f2bc$1279e150$958da70a@truly> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <001401c8f2bc$1279e150$958da70a@truly> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: chuli Cc: 'linux-audit' List-Id: linux-audit@redhat.com On Wednesday 30 July 2008 23:18:15 chuli wrote: > =C2=A0 When I use "auditctl -a exit,always -S 2015" in x86 system, this= rule can > be added. But I thought it would report error since there is not such > syscall number "1000" in x86, the max is 318.=20 We allow this because its possible that someone could write a kernel modu= le=20 (maybe not in Linus tree) that adds syscall numbers. While we wouldn't h= ave=20 a text interpretation for what it means, we thought that if this occurs t= hat=20 we would like to allow people to audit these new syscalls if they existed= .=20 Its otherwise harmless if you don't consider the performance hit. -Steve