From: Christoph Hellwig <hch@infradead.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Dmitry Kasatkin <d.kasatkin@samsung.com>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org, viro@ZenIV.linux.org.uk,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-security-module <linux-security-module@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Subject: Re: IMA: kernel reading files opened with O_DIRECT
Date: Wed, 2 Jul 2014 11:40:50 -0700 [thread overview]
Message-ID: <20140702184050.GA24583@infradead.org> (raw)
In-Reply-To: <x49y4wbu54y.fsf@segfault.boston.devel.redhat.com>
On Wed, Jul 02, 2014 at 11:55:41AM -0400, Jeff Moyer wrote:
> It's acceptable.
It's not because it will then also affect other reads going on at the
same time.
The whole concept of ima is just broken, and if you want to do these
sort of verification they need to happen inside the filesystem and not
above it.
We really should never have merged ima, and I think we should leave
these sorts of issue that have been there since day one unfixed and
deprecate it instead of adding workaround on top of workaround.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-07-02 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:40 Dmitry Kasatkin
2014-07-02 15:55 ` Jeff Moyer
2014-07-02 18:12 ` Dmitry Kasatkin
2014-07-02 18:40 ` Christoph Hellwig [this message]
2014-07-02 18:45 ` Jeff Moyer
2014-07-02 19:07 ` Dmitry Kasatkin
2014-07-11 20:10 ` Pavel Machek
2014-07-11 22:22 ` Dmitry Kasatkin
2014-07-15 13:03 ` Pavel Machek
2014-07-16 12:48 ` 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=20140702184050.GA24583@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=d.kasatkin@samsung.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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