From: hooanon05@yahoo.co.jp
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, James Morris <jmorris@namei.org>,
David Safford <safford@watson.ibm.com>,
Mimi Zohar <zohar@us.ibm.com>
Subject: Re: [PATCH] integrity: add ima_counts_put (updated)
Date: Fri, 03 Jul 2009 13:02:41 +0900 [thread overview]
Message-ID: <7465.1246593761@jrobl> (raw)
In-Reply-To: <1246313060.3280.81.camel@dyn9002018117.watson.ibm.com>
Mimi Zohar:
> NFSv3 is an interesting example. Permission checking is done once,
> followed by multiple open/read/close calls. Incrementing the counters in
> nfsd_permission() once and decrementing the counters in close, multiple
> times, resulted in imbalance messages. True, the solution in this case
> was to increment in open and decrement in close, but that was only part
> of the solution. The other part of the solution, the important part,
> was to add a call to ima_path_check() to measure the file.
Let me make sure.
Does "that was only part of the solution" mean IMA does not work for
NFSD fully? To make IMA work fully, is incrementing before open
absolutely necessary?
J. R. Okajima
next prev parent reply other threads:[~2009-07-03 4:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 15:24 [PATCH] integrity: add ima_counts_put Mimi Zohar
2009-06-26 18:05 ` [PATCH] integrity: add ima_counts_put (updated) Mimi Zohar
2009-06-28 22:50 ` James Morris
2009-06-29 11:08 ` Mimi Zohar
2009-06-29 14:12 ` hooanon05
2009-06-29 14:46 ` Mimi Zohar
2009-06-29 20:36 ` hooanon05
2009-06-29 22:04 ` Mimi Zohar
2009-07-03 4:02 ` hooanon05 [this message]
2009-07-03 18:37 ` Mimi Zohar
2009-07-29 5:12 ` hooanon05
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=7465.1246593761@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safford@watson.ibm.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