[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACE9dm_ARNNjCd=sM7VJ1k1H_cMYrPXd6mwttEOsMjeUb2c8mg@mail.gmail.com>
Date: Sat, 10 May 2014 20:30:53 +0300
From: Dmitry Kasatkin <dmitry.kasatkin@...il.com>
To: "J. R. Okajima" <hooanon05g@...il.com>
Cc: Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Dmitry Kasatkin <d.kasatkin@...sung.com>,
Al Viro <viro@...iv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
linux-security-module <linux-security-module@...r.kernel.org>,
eparis@...hat.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: IMA + O_DIRECT (Re: [PATCH 0/1] fix IMA + Apparmor kernel panic)
On 9 May 2014 23:07, J. R. Okajima <hooanon05g@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists