From: "Serge E. Hallyn" <serue@us.ibm.com>
To: linux-audit@redhat.com, amy.griffis@hp.com
Subject: Re: [PATCH 2/2] updated filesystem auditing patches for lspp test kernel
Date: Mon, 10 Apr 2006 12:56:26 -0500 [thread overview]
Message-ID: <20060410175626.GA27252@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20060407205653.GB29979@zk3.dec.com>
Hard to give this a meaningful review - particularly the first patch,
a large part of which seemed to be moving functionality from one file to
another. But slowly reading along, at least this smells like an error:
Quoting Amy Griffis (amy.griffis@hp.com):
> +/* Initialize a watch entry. */
> +static inline struct audit_watch *audit_init_watch(char *path)
> +{
> + struct audit_watch *watch;
> +
> + watch = kzalloc(sizeof(*watch), GFP_KERNEL);
> + if (unlikely(!watch))
> + return ERR_PTR(-ENOMEM);
...
> + watch = audit_init_watch(path);
> + if (unlikely(IS_ERR(watch)))
> + return PTR_ERR(watch);
Ok, but
> + new = audit_init_watch(path);
> + if (unlikely(!new)) {
> + kfree(path);
> + return ERR_PTR(-ENOMEM);
> + }
not ok
-serge
next prev parent reply other threads:[~2006-04-10 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 20:55 [PATCH 1/2] updated filesystem auditing patches for lspp test kernel Amy Griffis
2006-04-07 20:56 ` [PATCH 2/2] " Amy Griffis
2006-04-10 17:56 ` Serge E. Hallyn [this message]
2006-04-11 2:26 ` Amy Griffis
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=20060410175626.GA27252@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=amy.griffis@hp.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