[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140715130308.GA4109@amd.pavel.ucw.cz>
Date: Tue, 15 Jul 2014 15:03:08 +0200
From: Pavel Machek <pavel@....cz>
To: Dmitry Kasatkin <dmitry.kasatkin@...il.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Jeff Moyer <jmoyer@...hat.com>,
Dmitry Kasatkin <d.kasatkin@...sung.com>, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
akpm@...ux-foundation.org, Al Viro <viro@...iv.linux.org.uk>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
linux-security-module <linux-security-module@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: IMA: kernel reading files opened with O_DIRECT
On Sat 2014-07-12 01:22:04, Dmitry Kasatkin wrote:
> On 11 July 2014 23:10, Pavel Machek <pavel@....cz> wrote:
> > On Wed 2014-07-02 11:40:50, Christoph Hellwig wrote:
> >> 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.
> >
> > ...and doing it at filesystem layer would also permit verification of
> > per-block (64KB? 1MB?) hashes.
>
> Please design one single and the best universal filesystem which
> does it.
Given the overhead whole-file hashing has, you don't need single best
operating system. All you need it either ext4 or btrfs.. depending on
when you want it in production.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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