From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: audit_get_reply() returns EBADE
Date: Mon, 3 Mar 2008 16:04:46 -0500 [thread overview]
Message-ID: <200803031604.46111.sgrubb@redhat.com> (raw)
In-Reply-To: <47CBE074.9010706@redhat.com>
On Monday 03 March 2008 06:26:44 Matthew Booth wrote:
> A few times now I've seen audit_get_reply() return EBADE (Invalid
> exchange). This coincides with a particular job which results in an
> output rate of about 5.5k records/sec. The system remains responsive,
> and it always fixes itself when the rate comes back down again.
>
> What exactly does EBADE mean in this context?
No idea. A quick grep in the kernel source shows it only comes from a couple
places. bluetooth, sparc, and dlm are the main places. none of which seem to
be netlink related.
> I assume I'm dropping audit messages from the kernel while this is going on.
> Is there any way I can determine how many?
I think you'd have to patch the kernel to prove that to yourself.
> Is there any way to tune things to survive this temporary stress event?
I can't see how you are getting this in the first place. Have you grepped
around to see where its coming from?
-Steve
prev parent reply other threads:[~2008-03-03 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 11:26 audit_get_reply() returns EBADE Matthew Booth
2008-03-03 21:04 ` 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=200803031604.46111.sgrubb@redhat.com \
--to=sgrubb@redhat.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