From: Steve Grubb <sgrubb@redhat.com>
To: Hassan Sultan <hsultan@thefroid.net>
Cc: linux-audit@redhat.com
Subject: Re: multipart messages & delivery guarantees
Date: Mon, 23 Feb 2015 13:48:49 -0500 [thread overview]
Message-ID: <20150223134849.60cd7dc1@ivy-bridge> (raw)
In-Reply-To: <op.xuhpzho21jp0b1@win8mac>
On Sun, 22 Feb 2015 19:15:07 -0800
"Hassan Sultan" <hsultan@thefroid.net> wrote:
> Some events, such as execve or socket-related syscalls generate more
> than one message, which I'll separate as the "main" message, and then
> the 'sub' messages.
>
> Does the audit system guarantee in any way that user-mode will
> receive either no message, or all messages for a given event ?
If a syscall cannot be audited, the syscall has to fail.
> I'm curious to know if for example I could get an execve syscall
> message, but no cwd message, for example in case of low-memory
> condition.
I suppose it depends on where in the processing an error occurs. Some
failure modes if selected cause a system panic. You'll probably want to
look through the kernel source code to be sure.
-Steve
prev parent reply other threads:[~2015-02-23 18:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 3:15 multipart messages & delivery guarantees Hassan Sultan
2015-02-23 18:48 ` Steve Grubb [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=20150223134849.60cd7dc1@ivy-bridge \
--to=sgrubb@redhat.com \
--cc=hsultan@thefroid.net \
--cc=linux-audit@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