From: Eric Paris <eparis@redhat.com>
To: Marcelo Cerri <mhcerri@linux.vnet.ibm.com>
Cc: linux-audit@redhat.com
Subject: Re: Kernel oops+crash on repeated auditd restarts
Date: Mon, 23 Apr 2012 12:26:16 -0400 [thread overview]
Message-ID: <1335198376.8224.4.camel@localhost> (raw)
In-Reply-To: <20120420231424.1836e56b@oc8526070481.ibm.com>
On Fri, 2012-04-20 at 23:14 -0300, Marcelo Cerri wrote:
> The patch below increments the reference count of a mark when it is
> added to the destroy list. It seems to solve the issue and it doesn't
> seem to cause any memory leak. Please, can you make some tests in your
> environments and let me know if there is any problem with this patch.
That is almost certainly the wrong thing to do. This test program
should show a memory leak with your patch. If it doesn't show a memory
leak then something is screwed up in inotify as well.
#include <errno.h>
#include <unistd.h>
#include <sys/inotify.h>
int main(void)
{
int fd;
int rc;
struct inotify_event event[10];
fd = inotify_init();
if (fd < 0)
return errno;
while(1) {
rc = inotify_add_watch(fd, "/tmp", IN_CLOSE_WRITE);
if (rc < 0)
return errno;
rc = inotify_rm_watch(fd, rc);
if (rc)
return errno;
rc = read(fd, event, sizeof(event));
if (rc < 0)
return errno;
}
return 0;
}
The lifetime of an object is supposed to be from fsnotify_init_mark()
until it's matching reference is dropped in fsnotify_mark_destroy(). It
sounds to me like we are calling put somewhere in the audit code when we
didn't previously call a get....
next prev parent reply other threads:[~2012-04-23 16:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 16:45 Kernel oops+crash on repeated auditd restarts Valentin Avram
2012-01-25 16:53 ` Peter Moody
2012-01-25 19:20 ` Eric Paris
2012-01-26 7:13 ` Valentin Avram
2012-02-08 16:11 ` Valentin Avram
2012-03-05 8:35 ` Valentin Avram
2012-03-28 20:51 ` Peter Moody
2012-03-28 22:42 ` Peter Moody
2012-03-29 1:14 ` Eric Paris
2012-03-29 6:44 ` Valentin Avram
2012-04-03 16:15 ` Peter Moody
2012-04-05 21:03 ` Peter Moody
2012-04-05 21:07 ` Eric Paris
2012-04-17 17:56 ` Peter Moody
2012-04-17 18:24 ` Peter Moody
2012-04-17 21:54 ` Peter Moody
2012-04-21 2:14 ` Marcelo Cerri
2012-04-23 16:05 ` Peter Moody
2012-04-23 16:26 ` Eric Paris [this message]
2012-04-24 1:27 ` Peter Moody
2012-04-24 5:12 ` Marcelo Cerri
2012-04-24 18:31 ` Eric Paris
2012-04-24 18:38 ` Peter Moody
2012-04-24 19:06 ` Eric Paris
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=1335198376.8224.4.camel@localhost \
--to=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=mhcerri@linux.vnet.ibm.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