[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1288312226.2610.68.camel@localhost.localdomain>
Date: Thu, 28 Oct 2010 20:30:26 -0400
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: Eric Paris <eparis@...hat.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Chinner <david@...morbit.com>,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, hch@...radead.org,
warthog9@...nel.org, jmorris@...ei.org, kyle@...artin.ca,
hpa@...or.com, akpm@...ux-foundation.org, mingo@...e.hu,
viro@...iv.linux.org.uk, Matthew Wilcox <matthew@....cx>
Subject: Re: [PATCH 0/4] IMA: making i_readcount a first class inode citizen
On Thu, 2010-10-28 at 18:45 -0400, Eric Paris wrote:
> On Thu, 2010-10-28 at 15:29 -0700, Linus Torvalds wrote:
> > On Thu, Oct 28, 2010 at 3:24 PM, Dave Chinner <david@...morbit.com> wrote:
> > >
> > > Why the wrapper functions and locking? Why not an atomic variable like
> > > i_writecount?
> >
> > Indeed. With moving this more into the VFS, let's just make sure it
> > looks like i_writecount as much as possible.
>
> My thought was that the IMA read/write checks should happen AFTER the
> i_writecount and i_readcount counters were updated. Thus even if we
> raced with another task we can rest assured that the other task would
> catch the situation we missed....
>
> -Eric
Thanks Eric. My misunderstanding. Will update the patches, making
i_readcount atomic.
Mimi
--
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