| 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
| ||
|
Date: Tue, 26 Jun 2007 01:18:36 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: clameter@....com Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, Pekka Enberg <penberg@...helsinki.fi>, suresh.b.siddha@...el.com Subject: Re: [patch 15/26] Slab defrag: Support generic defragmentation for inode slab caches On Mon, 18 Jun 2007 02:58:53 -0700 clameter@....com wrote: > This implements the ability to remove inodes in a particular slab > from inode cache. In order to remove an inode we may have to write out > the pages of an inode, the inode itself and remove the dentries referring > to the node. > > Provide generic functionality that can be used by filesystems that have > their own inode caches to also tie into the defragmentation functions > that are made available here. Yes, this is tricky stuff. I have vague ancestral memories that the sort of inode work which you refer to here can cause various deadlocks, lockdep warnings and such nasties when if we attempt to call it from the wrong context (ie: from within fs code). Possibly we could prevent that by skipping all this code if the caller didn't have __GFP_FS. I trust all the code in kick_inodes() was carefuly copied from prue_icache() and such places - I didn't check it. - 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