From: Mimi Zohar <zohar@linux.ibm.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
Florent Revest <revest@chromium.org>,
linux-integrity@vger.kernel.org
Cc: jmorris@namei.org, serge@hallyn.com, revest@google.com,
allison@lohutok.net, armijn@tjaldur.nl, bauerman@linux.ibm.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] integrity: Expose data structures required for include/linux/integrity.h
Date: Tue, 17 Dec 2019 18:08:25 -0500 [thread overview]
Message-ID: <1576624105.4579.379.camel@linux.ibm.com> (raw)
In-Reply-To: <e9e366d3-6c5d-743b-ffde-6b95b85884a2@schaufler-ca.com>
On Tue, 2019-12-17 at 08:25 -0800, Casey Schaufler wrote:
> On 12/17/2019 5:47 AM, Florent Revest wrote:
> > From: Florent Revest <revest@google.com>
> >
> > include/linux/integrity.h exposes the prototype of integrity_inode_get().
> > However, it relies on struct integrity_iint_cache which is currently
> > defined in an internal header, security/integrity/integrity.h.
> >
> > To allow the rest of the kernel to use integrity_inode_get,
>
> Why do you want to do this?
ditto
>
> > this patch
> > moves the definition of the necessary structures from a private header
> > to a global kernel header.
> >
next prev parent reply other threads:[~2019-12-17 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 13:47 [PATCH] integrity: Expose data structures required for include/linux/integrity.h Florent Revest
2019-12-17 16:25 ` Casey Schaufler
2019-12-17 23:08 ` Mimi Zohar [this message]
2019-12-18 11:03 ` Florent Revest
2019-12-18 13:34 ` Mimi Zohar
2019-12-18 14:28 ` Mimi Zohar
2019-12-18 16:56 ` Florent Revest
2019-12-18 18:43 ` Mimi Zohar
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=1576624105.4579.379.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=allison@lohutok.net \
--cc=armijn@tjaldur.nl \
--cc=bauerman@linux.ibm.com \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=revest@chromium.org \
--cc=revest@google.com \
--cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).