From: Eric Paris <eparis@redhat.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>,
vibi sreenivasan <vibi_sreenivasan@cms.com>,
Jiri Slaby <jirislaby@gmail.com>,
David Safford <safford@watson.ibm.com>,
Mimi Zohar <zohar@us.ibm.com>
Subject: Re: [PATCH] integrity: ima audit dentry_open failure
Date: Thu, 04 Jun 2009 14:14:29 -0400 [thread overview]
Message-ID: <1244139269.2822.3.camel@dhcp231-142.rdu.redhat.com> (raw)
In-Reply-To: <1244137990-12678-1-git-send-email-zohar@linux.vnet.ibm.com>
On Thu, 2009-06-04 at 13:53 -0400, Mimi Zohar wrote:
> Until we start appraising measurements, the ima_path_check()
> return code should always be 0.
>
> - Update the ima_path_check() return code comment
> - Instead of the pr_info, audit the dentry_open failure
>
> Signed-off-by: Mimi Zohar <zohar@us.ibm.com>
So I'm not a big fan of the needless stack variable declaration. This
isn't the only spot you do it (and sometimes you do actually make use of
the variable like ima_add_template_entry) but I'm guessing the compiler
will clean it up, so
Acked-by: Eric Paris <eparis@redhat.com>
>
> ---
> security/integrity/ima/ima_main.c | 13 +++++++++----
> 1 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/security/integrity/ima/ima_main.c b/security/integrity/ima/ima_main.c
> index a2eb233..6f61187 100644
> --- a/security/integrity/ima/ima_main.c
> +++ b/security/integrity/ima/ima_main.c
> @@ -149,8 +149,8 @@ static void ima_update_counts(struct ima_iint_cache *iint, int mask)
> * - Opening a file for read when already open for write,
> * could result in a file measurement error.
> *
> - * Return 0 on success, an error code on failure.
> - * (Based on the results of appraise_measurement().)
> + * Always return 0 and audit dentry_open failures.
> + * (Return code will be based upon measurement appraisal.)
> */
> int ima_path_check(struct path *path, int mask, int update_counts)
> {
> @@ -189,8 +189,13 @@ int ima_path_check(struct path *path, int mask, int update_counts)
> file = dentry_open(dentry, mnt, O_RDONLY | O_LARGEFILE,
> current_cred());
> if (IS_ERR(file)) {
> - pr_info("%s dentry_open failed\n", dentry->d_name.name);
> - rc = PTR_ERR(file);
> + int audit_info = 0;
> +
> + integrity_audit_msg(AUDIT_INTEGRITY_PCR, inode,
> + dentry->d_name.name,
> + "add_measurement",
> + "dentry_open failed",
> + 1, audit_info);
> file = NULL;
> goto out;
> }
next prev parent reply other threads:[~2009-06-04 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 17:53 Mimi Zohar
2009-06-04 18:14 ` Eric Paris [this message]
2009-06-04 22:03 ` James Morris
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=1244139269.2822.3.camel@dhcp231-142.rdu.redhat.com \
--to=eparis@redhat.com \
--cc=jirislaby@gmail.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safford@watson.ibm.com \
--cc=vibi_sreenivasan@cms.com \
--cc=zohar@linux.vnet.ibm.com \
--cc=zohar@us.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
all inboxes | Powered by JetHome®