From: Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
To: "J. R. Okajima" <hooanon05g@gmail.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <d.kasatkin@samsung.com>,
Al Viro <viro@zeniv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-security-module <linux-security-module@vger.kernel.org>,
eparis@redhat.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: IMA + O_DIRECT (Re: [PATCH 0/1] fix IMA + Apparmor kernel panic)
Date: Sat, 10 May 2014 20:30:53 +0300 [thread overview]
Message-ID: <CACE9dm_ARNNjCd=sM7VJ1k1H_cMYrPXd6mwttEOsMjeUb2c8mg@mail.gmail.com> (raw)
In-Reply-To: <22172.1399666028@jrobl>
On 9 May 2014 23:07, J. R. Okajima <hooanon05g@gmail.com> wrote:
>
> Mimi Zohar:
>> I assume so, as there wasn't any comment. As a temporary fix, would it
>> make sense not to measure/appraise/audit files opened with the direct-io
>> flag based policy? Define a new IMA policy option 'directio'. A sample
>> rule would look like:
>>
>> dont_appraise bprm_check directio fsuuid=...
>
> I prefer such approach or anything addressing in IMA only, so it makes
> sense.
>
>
> J. R. Okajima
We are working on i_mutex free solution.
Let's hold on on this...
--
Thanks,
Dmitry
next prev parent reply other threads:[~2014-05-10 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 13:16 [PATCH 0/1] fix IMA + Apparmor kernel panic Dmitry Kasatkin
2014-05-08 13:16 ` [PATCH 1/1] ima: introduce ima_kernel_read() Dmitry Kasatkin
2014-05-13 18:01 ` Mimi Zohar
2014-05-09 3:10 ` IMA + O_DIRECT (Re: [PATCH 0/1] fix IMA + Apparmor kernel panic) J. R. Okajima
2014-05-09 8:14 ` Dmitry Kasatkin
2014-05-09 9:17 ` J. R. Okajima
2014-05-09 14:58 ` Mimi Zohar
2014-05-09 16:01 ` J. R. Okajima
2014-05-09 16:15 ` J. R. Okajima
2014-05-09 19:44 ` Mimi Zohar
2014-05-09 20:07 ` J. R. Okajima
2014-05-10 17:30 ` Dmitry Kasatkin [this message]
2014-05-09 17:56 ` Al Viro
2014-05-09 18:28 ` 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='CACE9dm_ARNNjCd=sM7VJ1k1H_cMYrPXd6mwttEOsMjeUb2c8mg@mail.gmail.com' \
--to=dmitry.kasatkin@gmail.com \
--cc=d.kasatkin@samsung.com \
--cc=ebiederm@xmission.com \
--cc=eparis@redhat.com \
--cc=hooanon05g@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@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;
as well as URLs for NNTP newsgroup(s).