From: "paul moore" <paulmoore100@hotmail.com>
To: linux-audit@redhat.com
Subject: listening to /dev/audit in a pthread program
Date: Fri, 20 Apr 2007 15:35:34 -0700 [thread overview]
Message-ID: <BAY119-DAV82AE30AFCDDC29FE452208C560@phx.gbl> (raw)
Message-ID: <000401c7839c$359b1040$656fa8c0@centrify.com> (raw)
I have an test app that quite happily does an audit_set_pid and then sits
there reading /dev/audit.
It works fine if its in the lead thread. But when I run the same code in my
real app it runs in a different thread. No matter what PID I pass to the
audit subsystem it complains that nobody is listening
I did audit_set_pid(....getpid...) - no (passes the pid of the manager
thread)
I did audit_set_pid(....gettid...) - no (passes the pid of the LWP)
(I dont really mean I did gettid - I did syscall(_NR_gettid))
I can see in the complaint message that I have given it the pid I intended
to.
I can see in gdb that my LWP id is the same as the one I send to the audit
subsystem - ie gettid worked.
Is this a known issue?
Heres the code snippet
void listen()
{
// register for events
pid_t mytid = (pid_t)syscall(__NR_gettid);
int res = audit_set_pid(m_auditFD, mytid, WAIT_YES);
res = audit_set_enabled(m_auditFD, 1);
assert(res >= 0);
static audit_reply reply;
while (true)
{
res = audit_get_reply(m_auditFD, &reply, GET_REPLY_BLOCKING, 0);
if (res < 0)
{
printf("exit audit %d %d\n", res, errno);
break;
}
printf("got event %.*s\n", reply.msg.nlh.nlmsg_len, reply.msg.data);
}
}
The thread sits waiting on the audit_get_reply call, so the FD is open
next reply other threads:[~2007-04-20 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000401c7839c$359b1040$656fa8c0@centrify.com>
2007-04-20 22:35 ` paul moore [this message]
2007-04-20 22:45 ` listening to /dev/audit in a pthread program Paul Moore
[not found] ` <000501c783a0$d14cdd30$656fa8c0@centrify.com>
2007-04-20 23:08 ` paul moore
2007-04-20 23:13 ` Steve Grubb
[not found] ` <000601c783a5$aef988a0$656fa8c0@centrify.com>
2007-04-20 23:43 ` paul moore
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=BAY119-DAV82AE30AFCDDC29FE452208C560@phx.gbl \
--to=paulmoore100@hotmail.com \
--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