From: "chuli" <chul@cn.fujitsu.com>
To: 'Steve Grubb' <sgrubb@redhat.com>
Cc: 'linux-audit' <linux-audit@redhat.com>
Subject: RE: Question about max syscall number
Date: Tue, 5 Aug 2008 15:13:14 +0800 [thread overview]
Message-ID: <004701c8f6ca$bca8b9a0$958da70a@truly> (raw)
In-Reply-To: <200808041546.12397.sgrubb@redhat.com>
Hi,
> We allow this because its possible that someone could write a kernel module
> (maybe not in Linus tree) that adds syscall numbers.
I see. Will it be added in the manual?
If I add a syscall whose number is 1000 in x86, such syscall can also be
auditd. And If I use ausearch -i -sc 1000 to lookup the log, the result is "
syscall=unknown syscall(1000)". Is it should be interpreted in the manual?
Regards
Chu Li
> -----Original Message-----
> From: Steve Grubb [mailto:sgrubb@redhat.com]
> Sent: Tuesday, August 05, 2008 3:46 AM
> To: chuli
> Cc: 'linux-audit'
> Subject: Re: Question about max syscall number
>
> On Wednesday 30 July 2008 23:18:15 chuli wrote:
> > 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.
>
> We allow this because its possible that someone could write a kernel module
> (maybe not in Linus tree) that adds syscall numbers. While we wouldn't have
> a text interpretation for what it means, we thought that if this occurs that
> we would like to allow people to audit these new syscalls if they existed.
> Its otherwise harmless if you don't consider the performance hit.
>
> -Steve
next prev parent reply other threads:[~2008-08-05 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 3:18 Question about max syscall number chuli
2008-08-04 3:06 ` [PATCH]Fix the bug about checking the " chuli
2008-08-04 19:46 ` Question about max " Steve Grubb
2008-08-05 7:13 ` chuli [this message]
2008-08-05 13:58 ` Steve Grubb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='004701c8f6ca$bca8b9a0$958da70a@truly' \
--to=chul@cn.fujitsu.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox