From: Steve Grubb <sgrubb@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-audit@redhat.com, pmoore@hp.com
Subject: Re: [PATCH] Audit: EINTR instead of kernel private return codes in audit records
Date: Sun, 18 Nov 2007 05:58:16 -0500 [thread overview]
Message-ID: <200711180558.16921.sgrubb@redhat.com> (raw)
In-Reply-To: <1195351113.2924.120.camel@localhost.localdomain>
On Saturday 17 November 2007 08:58:33 pm Eric Paris wrote:
> It would be absolutely wrong for the audit system to translate
> even ENOIOCTLCMD to anything else if this is what was actually returned
> to the process.
The point is, none of the errnos in that file should *ever* go to user space.
glibc has no translation (strerror()) for them because they are internal to
the kernel. So, they need to get translated to something. My only question is
would these extra ones ever get picked up in this code path?
-Steve
next prev parent reply other threads:[~2007-11-18 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 20:22 [PATCH] Audit: EINTR instead of kernel private return codes in audit records Eric Paris
2007-11-14 20:29 ` Paul Moore
2007-11-14 20:30 ` Steve Grubb
2007-11-14 21:07 ` Eric Paris
2007-11-14 21:17 ` Steve Grubb
2007-11-18 1:58 ` Eric Paris
2007-11-18 10:58 ` Steve Grubb [this message]
2007-11-18 16:52 ` Eric Paris
2007-11-14 21:13 ` Miloslav Trmac
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=200711180558.16921.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=pmoore@hp.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