From: Guido Trentalancia <guido@trentalancia.com>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: avc's generated causes the system to freeze up
Date: Sun, 13 Dec 2009 20:40:23 +0100 [thread overview]
Message-ID: <1260733223.2858.23.camel@tesla.lan> (raw)
In-Reply-To: <4B252E41.6070501@gmail.com>
Have you tried tuning auditd and its dispatcher which could be audispd ?
So for example, try feeding audispd with the following options:
q_depth: increase it from its default value (which is 80 on Redhat's
recent auditd)
priority_boost = 0
Finally, if things don't improve, you could also try:
overflow_action = suspend
Other than this I don't know how to help. Good luck.
On Sun, 2009-12-13 at 10:11 -0800, Justin P. Mattock wrote:
> On 12/13/09 08:42, Guido Trentalancia wrote:
> > Justin,
> >
> > your question seems more of an audit question.
> >
> > Why don't you use audit2allow to sort this out from a SELinux point of
> > view instead than trying to shut up audit ?
> >
> > Audit2allow can generate custom rules for you from the analysis of your
> > audit log messages. The rules can then be compiled into a custom policy
> > module, that you can install with semodule.
> >
> >
>
> I can easily create an allow rule with audit2allow.
>
> The issue is not creating an allow rule,
> but having Xorg.0.log spammed with a denial
> causing the system to freeze up, until
> the avc is done doing with whatever it's doing
> (in this case logging many denials of the same one).
>
> hence the reason for wondering if theres a mechanism that could
> be put in place like prinkt_ratelimit for
> Xorg.0.log this way I don't get spammed with a denial.
>
> Justin P. Mattock
>
>
>
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2009-12-13 19:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 21:44 avc's generated causes the system to freeze up Justin Mattock
2009-12-11 21:44 ` [refpolicy] " Justin Mattock
2009-12-13 16:42 ` Guido Trentalancia
2009-12-13 18:11 ` Justin P. Mattock
2009-12-13 19:40 ` Guido Trentalancia [this message]
2009-12-13 20:23 ` Justin P. Mattock
2009-12-14 9:56 ` Guido Trentalancia
2009-12-14 16:11 ` Justin P. Mattock
2009-12-14 16:15 ` Guido Trentalancia
2009-12-14 17:15 ` Justin P. Mattock
2009-12-14 17:15 ` [refpolicy] " Justin P. Mattock
2009-12-14 17:37 ` Eamon Walsh
2009-12-14 17:37 ` [refpolicy] " Eamon Walsh
2009-12-14 18:39 ` Justin P. Mattock
2009-12-14 18:39 ` [refpolicy] " Justin P. Mattock
2009-12-14 18:39 ` Xavier Toth
2009-12-14 18:39 ` [refpolicy] " Xavier Toth
2009-12-14 19:13 ` Justin P. Mattock
2009-12-14 19:13 ` [refpolicy] " Justin P. Mattock
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=1260733223.2858.23.camel@tesla.lan \
--to=guido@trentalancia.com \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.