| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1288305907.3017.1.camel@localhost.localdomain> Date: Thu, 28 Oct 2010 18:45:07 -0400 From: Eric Paris <eparis@...hat.com> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Dave Chinner <david@...morbit.com>, Mimi Zohar <zohar@...ux.vnet.ibm.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 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 -- 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