All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Vincas Dargis <vindrg@gmail.com>
Cc: linux-audit@redhat.com
Subject: Re: aureport endless loop with specific input on Debian 8
Date: Sat, 5 Nov 2016 14:37:02 +0000	[thread overview]
Message-ID: <20161105143702.07cc65e2@ivy-bridge> (raw)
In-Reply-To: <4cb61e99-f114-d48a-768f-70e7e1df4331@gmail.com>

On Sat, 5 Nov 2016 15:05:32 +0200
Vincas Dargis <vindrg@gmail.com> wrote:
> 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.

If I read that correctly, this is against audit-2.4. There was linked
list fixes to ausearch/report in 2.4.4. I suspect that fixes your bug
report. Its not reproducible with the latest version.

-Steve

 
> 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
> 
> --
> Linux-audit mailing list
> Linux-audit@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-audit

  reply	other threads:[~2016-11-05 14:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 13:05 aureport endless loop with specific input on Debian 8 Vincas Dargis
2016-11-05 14:37 ` Steve Grubb [this message]
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=20161105143702.07cc65e2@ivy-bridge \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=vindrg@gmail.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 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.