From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
parisc-linux@lists.parisc-linux.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, Ollie Wild <aaw@google.com>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@suse.de>,
linux-audit@redhat.com
Subject: Re: [patch 2/3] audit: rework execve audit
Date: Tue, 03 Jul 2007 17:00:55 +0200 [thread overview]
Message-ID: <1183474855.7054.2.camel@twins> (raw)
In-Reply-To: <20070626155541.9708eded.akpm@linux-foundation.org>
On Tue, 2007-06-26 at 15:55 -0700, Andrew Morton wrote:
> On Wed, 13 Jun 2007 12:03:36 +0200
> Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> > +#ifdef CONFIG_AUDITSYSCALL
> > + {
> > + .ctl_name = CTL_UNNUMBERED,
> > + .procname = "audit_argv_kb",
> > + .data = &audit_argv_kb,
> > + .maxlen = sizeof(int),
> > + .mode = 0644,
> > + .proc_handler = &proc_dointvec,
> > + },
> > +#endif
>
> Please document /proc entries in Documentation/filesystems/proc.txt
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
Documentation/filesystems/proc.txt | 7 +++++++
1 file changed, 7 insertions(+)
Index: linux-2.6/Documentation/filesystems/proc.txt
===================================================================
--- linux-2.6.orig/Documentation/filesystems/proc.txt
+++ linux-2.6/Documentation/filesystems/proc.txt
@@ -1075,6 +1075,13 @@ check the amount of free space (value is
resume it if we have a value of 3 or more percent; consider information about
the amount of free space valid for 30 seconds
+audit_argv_kb
+-------------
+
+The file contains a single value denoting the limit on the argv array size
+for execve (in KiB). This limit is only applied when system call auditing for
+execve is enabled, otherwise the value is ignored.
+
ctrl-alt-del
------------
next prev parent reply other threads:[~2007-07-03 15:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 10:03 [patch 0/3] no MAX_ARG_PAGES -v2 Peter Zijlstra
2007-06-13 10:03 ` [patch 1/3] arch: personality independent stack top Peter Zijlstra
2007-06-13 10:03 ` [patch 2/3] audit: rework execve audit Peter Zijlstra
2007-06-26 22:55 ` Andrew Morton
2007-07-03 15:00 ` Peter Zijlstra [this message]
2007-06-13 10:03 ` [patch 3/3] mm: variable length argument support Peter Zijlstra
2007-08-07 19:03 ` Olaf Hering
2007-08-07 19:20 ` Andrew Morton
2007-08-07 19:26 ` Peter Zijlstra
2007-08-07 20:10 ` Olaf Hering
2007-08-22 8:48 ` Dan Aloni
2007-08-22 8:54 ` Peter Zijlstra
2007-08-22 9:05 ` Andrew Morton
[not found] ` <20070822090251.GA7038@mail.ustc.edu.cn>
2007-08-22 9:02 ` Fengguang Wu
2007-06-13 23:36 ` [patch 0/3] no MAX_ARG_PAGES -v2 Luck, Tony
2007-06-14 6:23 ` Ollie Wild
2007-06-14 8:38 ` Peter Zijlstra
2007-06-14 18:22 ` Luck, Tony
2007-06-14 18:32 ` Peter Zijlstra
2007-06-14 20:58 ` Ollie Wild
2007-06-14 21:18 ` Peter Zijlstra
2007-06-15 9:24 ` Peter Zijlstra
2007-06-15 18:07 ` Ollie Wild
2007-06-15 18:49 ` Luck, Tony
2007-06-17 18:32 ` Pavel Machek
2007-06-17 19:07 ` Ingo Molnar
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=1183474855.7054.2.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=aaw@google.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=parisc-linux@lists.parisc-linux.org \
/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;
as well as URLs for NNTP newsgroup(s).