| 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: <20101109213619.GA3246@amd> Date: Wed, 10 Nov 2010 08:36:19 +1100 From: Nick Piggin <npiggin@...nel.dk> To: Andi Kleen <andi@...stfloor.org> Cc: Nick Piggin <npiggin@...nel.dk>, Al Viro <viro@...IV.linux.org.uk>, Linus Torvalds <torvalds@...ux-foundation.org>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: [patch 1/6] fs: icache RCU free inodes On Tue, Nov 09, 2010 at 03:19:02PM +0100, Andi Kleen wrote: > Nick Piggin <npiggin@...nel.dk> writes: > > > So here is the inode RCU code. It's obviously not worth doing until the > > actual rcu-walk path walking is in, but I'd like to get opinions on it. > > It would be nice to merge it in Al's tree at some point, though. > > I read the patch. It was quite monotonous (I guess that's a good thing) > But it wasn't clear to me why you added the INIT_LIST_HEAD()s > everywhere. Is this for stopping parallel walkers? > > Ok there's a comment in the doc: "VFS expects it to be initialized" > Is that really true today? I don't think the old code does that. It is in the inode_init_once pile, so yes it has to be returned to the allocator initialized. > > Other than that it seems straight forward. > > Reviewed-by: Andi Kleen <ak@...ux.intel.com> Thanks, Nick -- 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