From: Vincas Dargis <vindrg@gmail.com>
To: linux-audit@redhat.com
Subject: aureport endless loop with specific input on Debian 8
Date: Sat, 5 Nov 2016 15:05:32 +0200 [thread overview]
Message-ID: <4cb61e99-f114-d48a-768f-70e7e1df4331@gmail.com> (raw)
Hi,
I have reported bug in Debian bug tracker [1] that after upgrading to Debian 8, aureport does not finish it's
"reporting" for hours one some inputs, generated by ausearch. It's stuck with 100% CPU usage.
Since maintainer haven't responded yet, I though I could try for help directly here.
More info, and two example input files for reproducing attached in same bug report.
I wonder, would it be... "reasonable" to hope for some kind isolated patch that Debian maintainer could apply and
release fix for Debian 8 which is currently in "stable" mode? I know it's kinda not the mailing list to ask about it,
but maybe you have experience in that regard?
Thanks!
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841272
next reply other threads:[~2016-11-05 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 13:05 Vincas Dargis [this message]
2016-11-05 14:37 ` aureport endless loop with specific input on Debian 8 Steve Grubb
2016-11-05 17:30 ` Steve Grubb
2016-11-06 10:22 ` Vincas Dargis
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=4cb61e99-f114-d48a-768f-70e7e1df4331@gmail.com \
--to=vindrg@gmail.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