From: Linda Knippers <linda.knippers@hp.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: offsets for 64bit IPC mechanisms
Date: Wed, 10 Jan 2007 11:21:45 -0500 [thread overview]
Message-ID: <45A51299.7040602@hp.com> (raw)
In-Reply-To: <200701101113.07852.sgrubb@redhat.com>
> OK, that's fine with me. But I wonder where all this should be documented so
> that we don't get bugzilla's opened by concerned users. Would any particular
> man page be better than others?
Perhaps the auditctl manpage should be clear (if it isn't already) that
its auditing the kernel arguments so they may be different than what was
passed into a library routine of the same name. Maybe give an example.
This specific one is documented in the Notes section of the semctl(2)
and msgctl(2) manpages, which I think is the right place for the
details. If someone wants to audit a specific syscall, they should
make sure they understand how the syscall works.
-- ljk
prev parent reply other threads:[~2007-01-10 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 16:02 offsets for 64bit IPC mechanisms Steve Grubb
2007-01-10 16:08 ` Linda Knippers
2007-01-10 16:13 ` Steve Grubb
2007-01-10 16:21 ` Linda Knippers [this message]
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=45A51299.7040602@hp.com \
--to=linda.knippers@hp.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