)]}' { "log": [ { "commit": "05dafedb906425fe935199f4c92700d87285e3e9", "tree": "7f3162455188c322baf9c6ca9a2890394380201d", "parents": [ "94e0fb086fc5663c38bbc0fe86d698be8314f82f" ], "author": { "name": "Roland Dreier", "email": "roland@digitalvampire.org", "time": "Tue Jul 14 13:32:56 2009 -0700" }, "committer": { "name": "Tyler Hicks", "email": "tyhicks@linux.vnet.ibm.com", "time": "Wed Sep 23 09:10:30 2009 -0500" }, "message": "ecryptfs: Remove unneeded locking that triggers lockdep false positives\n\nIn ecryptfs_destroy_inode(), inode_info-\u003elower_file_mutex is locked,\nand just after the mutex is unlocked, the code does:\n\n \tkmem_cache_free(ecryptfs_inode_info_cache, inode_info);\n\nThis means that if another context could possibly try to take the same\nmutex as ecryptfs_destroy_inode(), then it could end up getting the\nmutex just before the data structure containing the mutex is freed.\nSo any such use would be an obvious use-after-free bug (catchable with\nslab poisoning or mutex debugging), and therefore the locking in\necryptfs_destroy_inode() is not needed and can be dropped.\n\nSimilarly, in ecryptfs_destroy_crypt_stat(), crypt_stat-\u003ekeysig_list_mutex\nis locked, and then the mutex is unlocked just before the code does:\n\n \tmemset(crypt_stat, 0, sizeof(struct ecryptfs_crypt_stat));\n\nTherefore taking this mutex is similarly not necessary.\n\nRemoving this locking fixes false-positive lockdep reports such as the\nfollowing (and they are false-positives for exactly the same reason\nthat the locking is not needed):\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n[ INFO: inconsistent lock state ]\n2.6.31-2-generic #14~rbd3\n---------------------------------\ninconsistent {RECLAIM_FS-ON-W} -\u003e {IN-RECLAIM_FS-W} usage.\nkswapd0/323 [HC0[0]:SC0[0]:HE1:SE1] takes:\n (\u0026inode_info-\u003elower_file_mutex){+.+.?.}, at: [\u003cffffffff81210d34\u003e] ecryptfs_destroy_inode+0x34/0x100\n{RECLAIM_FS-ON-W} state was registered at:\n [\u003cffffffff8108c02c\u003e] mark_held_locks+0x6c/0xa0\n [\u003cffffffff8108c10f\u003e] lockdep_trace_alloc+0xaf/0xe0\n [\u003cffffffff81125a51\u003e] kmem_cache_alloc+0x41/0x1a0\n [\u003cffffffff8113117a\u003e] get_empty_filp+0x7a/0x1a0\n [\u003cffffffff8112dd46\u003e] dentry_open+0x36/0xc0\n [\u003cffffffff8121a36c\u003e] ecryptfs_privileged_open+0x5c/0x2e0\n [\u003cffffffff81210283\u003e] ecryptfs_init_persistent_file+0xa3/0xe0\n [\u003cffffffff8120e838\u003e] ecryptfs_lookup_and_interpose_lower+0x278/0x380\n [\u003cffffffff8120f97a\u003e] ecryptfs_lookup+0x12a/0x250\n [\u003cffffffff8113930a\u003e] real_lookup+0xea/0x160\n [\u003cffffffff8113afc8\u003e] do_lookup+0xb8/0xf0\n [\u003cffffffff8113b518\u003e] __link_path_walk+0x518/0x870\n [\u003cffffffff8113bd9c\u003e] path_walk+0x5c/0xc0\n [\u003cffffffff8113be5b\u003e] do_path_lookup+0x5b/0xa0\n [\u003cffffffff8113bfe7\u003e] user_path_at+0x57/0xa0\n [\u003cffffffff811340dc\u003e] vfs_fstatat+0x3c/0x80\n [\u003cffffffff8113424b\u003e] vfs_stat+0x1b/0x20\n [\u003cffffffff81134274\u003e] sys_newstat+0x24/0x50\n [\u003cffffffff81013132\u003e] system_call_fastpath+0x16/0x1b\n [\u003cffffffffffffffff\u003e] 0xffffffffffffffff\nirq event stamp: 7811\nhardirqs last enabled at (7811): [\u003cffffffff810c037f\u003e] call_rcu+0x5f/0x90\nhardirqs last disabled at (7810): [\u003cffffffff810c0353\u003e] call_rcu+0x33/0x90\nsoftirqs last enabled at (3764): [\u003cffffffff810631da\u003e] __do_softirq+0x14a/0x220\nsoftirqs last disabled at (3751): [\u003cffffffff8101440c\u003e] call_softirq+0x1c/0x30\n\nother info that might help us debug this:\n2 locks held by kswapd0/323:\n #0: (shrinker_rwsem){++++..}, at: [\u003cffffffff810f67ed\u003e] shrink_slab+0x3d/0x190\n #1: (\u0026type-\u003es_umount_key#35){.+.+..}, at: [\u003cffffffff811429a1\u003e] prune_dcache+0xd1/0x1b0\n\nstack backtrace:\nPid: 323, comm: kswapd0 Tainted: G C 2.6.31-2-generic #14~rbd3\nCall Trace:\n [\u003cffffffff8108ad6c\u003e] print_usage_bug+0x18c/0x1a0\n [\u003cffffffff8108aff0\u003e] ? check_usage_forwards+0x0/0xc0\n [\u003cffffffff8108bac2\u003e] mark_lock_irq+0xf2/0x280\n [\u003cffffffff8108bd87\u003e] mark_lock+0x137/0x1d0\n [\u003cffffffff81164710\u003e] ? fsnotify_clear_marks_by_inode+0x30/0xf0\n [\u003cffffffff8108bee6\u003e] mark_irqflags+0xc6/0x1a0\n [\u003cffffffff8108d337\u003e] __lock_acquire+0x287/0x430\n [\u003cffffffff8108d585\u003e] lock_acquire+0xa5/0x150\n [\u003cffffffff81210d34\u003e] ? ecryptfs_destroy_inode+0x34/0x100\n [\u003cffffffff8108d2e7\u003e] ? __lock_acquire+0x237/0x430\n [\u003cffffffff815526ad\u003e] __mutex_lock_common+0x4d/0x3d0\n [\u003cffffffff81210d34\u003e] ? ecryptfs_destroy_inode+0x34/0x100\n [\u003cffffffff81164710\u003e] ? fsnotify_clear_marks_by_inode+0x30/0xf0\n [\u003cffffffff81210d34\u003e] ? ecryptfs_destroy_inode+0x34/0x100\n [\u003cffffffff8129a91e\u003e] ? _raw_spin_unlock+0x5e/0xb0\n [\u003cffffffff81552b36\u003e] mutex_lock_nested+0x46/0x60\n [\u003cffffffff81210d34\u003e] ecryptfs_destroy_inode+0x34/0x100\n [\u003cffffffff81145d27\u003e] destroy_inode+0x87/0xd0\n [\u003cffffffff81146b4c\u003e] generic_delete_inode+0x12c/0x1a0\n [\u003cffffffff81145832\u003e] iput+0x62/0x70\n [\u003cffffffff811423c8\u003e] dentry_iput+0x98/0x110\n [\u003cffffffff81142550\u003e] d_kill+0x50/0x80\n [\u003cffffffff81142623\u003e] prune_one_dentry+0xa3/0xc0\n [\u003cffffffff811428b1\u003e] __shrink_dcache_sb+0x271/0x290\n [\u003cffffffff811429d9\u003e] prune_dcache+0x109/0x1b0\n [\u003cffffffff81142abf\u003e] shrink_dcache_memory+0x3f/0x50\n [\u003cffffffff810f68dd\u003e] shrink_slab+0x12d/0x190\n [\u003cffffffff810f9377\u003e] balance_pgdat+0x4d7/0x640\n [\u003cffffffff8104c4c0\u003e] ? finish_task_switch+0x40/0x150\n [\u003cffffffff810f63c0\u003e] ? isolate_pages_global+0x0/0x60\n [\u003cffffffff810f95f7\u003e] kswapd+0x117/0x170\n [\u003cffffffff810777a0\u003e] ? autoremove_wake_function+0x0/0x40\n [\u003cffffffff810f94e0\u003e] ? kswapd+0x0/0x170\n [\u003cffffffff810773be\u003e] kthread+0x9e/0xb0\n [\u003cffffffff8101430a\u003e] child_rip+0xa/0x20\n [\u003cffffffff81013c90\u003e] ? restore_args+0x0/0x30\n [\u003cffffffff81077320\u003e] ? kthread+0x0/0xb0\n [\u003cffffffff81014300\u003e] ? child_rip+0x0/0x20\n\nSigned-off-by: Roland Dreier \u003croland@digitalvampire.org\u003e\nSigned-off-by: Tyler Hicks \u003ctyhicks@linux.vnet.ibm.com\u003e\n" }, { "commit": "6cfd0148425e528b859b26e436b01f23f6926224", "tree": "60e3257053554ff198fe5825e6f12a00c3b4422a", "parents": [ "a9e220f8322e2b0e0b8903fe00265461cffad3f0" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue May 05 15:40:36 2009 +0200" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Jun 11 21:36:07 2009 -0400" }, "message": "push BKL down into -\u003eput_super\n\nMove BKL into -\u003eput_super from the only caller. A couple of\nfilesystems had trivial enough -\u003eput_super (only kfree and NULLing of\ns_fs_info + stuff in there) to not get any locking: coda, cramfs, efs,\nhugetlbfs, omfs, qnx4, shmem, all others got the full treatment. Most\nof them probably don\u0027t need it, but I\u0027d rather sort that out individually.\nPreferably after all the other BKL pushdowns in that area.\n\n[AV: original used to move lock_super() down as well; these changes are\nremoved since we don\u0027t do lock_super() at all in generic_shutdown_super()\nnow]\n[AV: fuse, btrfs and xfs are known to need no damn BKL, exempt]\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "e77cc8d243f9f1e1d3f0799e23cc14e837ccc8c6", "tree": "e71815e09c73e33bdd2c687f7508e3720c4d3ed7", "parents": [ "13a791b4e63eb0537a7f804a340d6527485983b4" ], "author": { "name": "Tyler Hicks", "email": "tyhicks@linux.vnet.ibm.com", "time": "Wed Apr 22 04:08:46 2009 -0500" }, "committer": { "name": "Tyler Hicks", "email": "tyhicks@linux.vnet.ibm.com", "time": "Wed Apr 22 04:08:46 2009 -0500" }, "message": "eCryptfs: Remove ecryptfs_unlink_sigs warnings\n\nA feature was added to the eCryptfs umount helper to automatically\nunlink the keys used for an eCryptfs mount from the kernel keyring upon\numount. This patch keeps the unrecognized mount option warnings for\necryptfs_unlink_sigs out of the logs.\n\nSigned-off-by: Tyler Hicks \u003ctyhicks@linux.vnet.ibm.com\u003e\n" }, { "commit": "3a5203ab3c0c31e0f1434c69e893bfb85c6e6657", "tree": "76edf493f4737f57448e5705cd7d29fddeb4a66a", "parents": [ "57ea34d19963781d05eb12f9b31bd4f70d61ec16" ], "author": { "name": "Tyler Hicks", "email": "tyhicks@linux.vnet.ibm.com", "time": "Mon Mar 16 12:35:12 2009 -0500" }, "committer": { "name": "Tyler Hicks", "email": "tyhicks@linux.vnet.ibm.com", "time": "Wed Apr 22 03:54:13 2009 -0500" }, "message": "eCryptfs: Print FNEK sig properly in /proc/mounts\n\nThe filename encryption key signature is not properly displayed in\n/proc/mounts. The \"ecryptfs_sig\u003d\" mount option name is displayed for\nall global authentication tokens, included those for filename keys.\n\nThis patch checks the global authentication token flags to determine if\nthe key is a FEKEK or FNEK and prints the appropriate mount option name\nbefore the signature.\n\nSigned-off-by: Tyler Hicks \u003ctyhicks@linux.vnet.ibm.com\u003e\n" }, { "commit": "2830bfd6cf66133c86d4a32004fd99c3de7e23bf", "tree": "51f68453ad6b5a3a75667385369bbd9b5ba8a02c", "parents": [ "99db6e4a9764887842006a2b1aa804de6171db42" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Wed Feb 06 01:38:34 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Feb 06 10:41:12 2008 -0800" }, "message": "ecryptfs: remove debug as mount option, and warn if set via modprobe\n\necryptfs_debug really should not be a mount option; it is not per-mount,\nbut rather sets a global \"ecryptfs_verbosity\" variable which affects all\nmounted filesysytems. It\u0027s already settable as a module load option,\nI think we can leave it at that.\n\nAlso, if set, since secret values come out in debug messages, kick\nthings off with a stern warning.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nAcked-by: Mike Halcrow \u003cmhalcrow@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "99db6e4a9764887842006a2b1aa804de6171db42", "tree": "5d45cd3f74aaeeb9209dea2e9a00d197d4e2cc06", "parents": [ "8e3a6f16ba5874b69968cd450334829262513fd1" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Wed Feb 06 01:38:34 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Feb 06 10:41:12 2008 -0800" }, "message": "ecryptfs: make show_options reflect actual mount options\n\nChange ecryptfs_show_options to reflect the actual mount options in use.\nNote that this does away with the \"dir\u003d\" output, which is not a valid mount\noption and appears to be unused.\n\nMount options such as \"ecryptfs_verbose\" and \"ecryptfs_xattr_metadata\" are\nsomewhat indeterminate for a given fs, but in any case the reported mount\noptions can be used in a new mount command to get the same behavior.\n\n[akpm@linux-foundation.org: fix printk warning]\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nAcked-by: Michael Halcrow \u003cmhalcrow@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "caeeeecfdaeada2998eb3c29c3ebd59afb79ef06", "tree": "22b7931ba119d10fb9c76bc54b500ce1d43d505c", "parents": [ "c51b1a160b63304720d49479986915e4c475a2cf" ], "author": { "name": "Michael Halcrow", "email": "mhalcrow@us.ibm.com", "time": "Tue Jan 08 15:33:02 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Jan 08 16:10:36 2008 -0800" }, "message": "eCryptfs: fix dentry handling on create error, unlink, and inode destroy\n\nThis patch corrects some erroneous dentry handling in eCryptfs.\n\nIf there is a problem creating the lower file, then there is nothing that\nthe persistent lower file can do to really help us. This patch makes a\nvfs_create() failure in the lower filesystem always lead to an\nunconditional do_create failure in eCryptfs.\n\nUnder certain sequences of operations, the eCryptfs dentry can remain in\nthe dcache after an unlink. This patch calls d_drop() on the eCryptfs\ndentry to correct this.\n\neCryptfs has no business calling d_delete() directly on a lower\nfilesystem\u0027s dentry. This patch removes the call to d_delete() on the\nlower persistent file\u0027s dentry in ecryptfs_destroy_inode().\n\n(Thanks to David Kleikamp, Eric Sandeen, and Jeff Moyer for helping\nidentify and resolve this issue)\n\nSigned-off-by: Michael Halcrow \u003cmhalcrow@us.ibm.com\u003e\nCc: Dave Kleikamp \u003cshaggy@austin.ibm.com\u003e\nCc: Eric Sandeen \u003csandeen@redhat.com\u003e\nCc: Jeff Moyer \u003cjmoyer@redhat.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "035241d30e273519195a9987e6eb56bbe2297872", "tree": "56865416d10597588c00957766d3e6189b19a014", "parents": [ "d6a13c17164fccab8aa96ca435ddacbf428335ca" ], "author": { "name": "Michael Halcrow", "email": "mhalcrow@us.ibm.com", "time": "Tue Oct 16 01:28:12 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Oct 16 09:43:12 2007 -0700" }, "message": "eCryptfs: initialize persistent lower file on inode create\n\nInitialize persistent lower file on inode create.\n\nSigned-off-by: Michael Halcrow \u003cmhalcrow@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "4981e081cfe2c3f4abcfa3924ebd999cdbed4914", "tree": "066d56ba49195eb0e733236fef4bb98f2d5f0114", "parents": [ "0216f7f7921759211e48e8b940eae29f0fe43902" ], "author": { "name": "Michael Halcrow", "email": "mhalcrow@us.ibm.com", "time": "Tue Oct 16 01:28:09 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Oct 16 09:43:12 2007 -0700" }, "message": "eCryptfs: set up and destroy persistent lower file\n\nThis patch sets up and destroys the persistent lower file for each eCryptfs\ninode.\n\nSigned-off-by: Michael Halcrow \u003cmhalcrow@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "fcd12835666b059b95613778819eb3ae9bc73642", "tree": "bd825395368d5039e039f930288b3997a2a96263", "parents": [ "af655dc6a9d5028d89aa35b65781631451aadc19" ], "author": { "name": "Michael Halcrow", "email": "mhalcrow@us.ibm.com", "time": "Tue Oct 16 01:28:01 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Oct 16 09:43:11 2007 -0700" }, "message": "eCryptfs: grammatical fix (destruct to destroy)\n\nAndrew Morton wrote:\n\u003e \u003e +int ecryptfs_destruct_crypto(void)\n\u003e\n\u003e ecryptfs_destroy_crypto would be more grammatically correct ;)\n\nGrammatical fix for some function names.\n\nSigned-off-by: Michael Halcrow \u003cmhalcrow@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "ee9b6d61a2a43c5952eb43283f8db284a4e70b8a", "tree": "afb0340e79d3e9d14f39df20e165ce2efe941b18", "parents": [ "c5ef1c42c51b1b5b4a401a6517bdda30933ddbaf" ], "author": { "name": "Josef \u0027Jeff\u0027 Sipek", "email": "jsipek@cs.sunysb.edu", "time": "Mon Feb 12 00:55:41 2007 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Mon Feb 12 09:48:47 2007 -0800" }, "message": "[PATCH] Mark struct super_operations const\n\nThis patch is inspired by Arjan\u0027s \"Patch series to mark struct\nfile_operations and struct inode_operations const\".\n\nCompile tested with gcc \u0026 sparse.\n\nSigned-off-by: Josef \u0027Jeff\u0027 Sipek \u003cjsipek@cs.sunysb.edu\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "e94b1766097d53e6f3ccfb36c8baa562ffeda3fc", "tree": "93fa0a8ab84976d4e89c50768ca8b8878d642a0d", "parents": [ "54e6ecb23951b195d02433a741c7f7cb0b796c78" ], "author": { "name": "Christoph Lameter", "email": "clameter@sgi.com", "time": "Wed Dec 06 20:33:17 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.osdl.org", "time": "Thu Dec 07 08:39:24 2006 -0800" }, "message": "[PATCH] slab: remove SLAB_KERNEL\n\nSLAB_KERNEL is an alias of GFP_KERNEL.\n\nSigned-off-by: Christoph Lameter \u003cclameter@sgi.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "316bb95e8ed0ddcd767e8aa54264b6c6190f150c", "tree": "6dc89abf8c1d64a61481cbaa288ad2f3afcf51e9", "parents": [ "7ff1d74f5670329ac4b5959a675f8698ba95be20" ], "author": { "name": "Michael Halcrow", "email": "mhalcrow@us.ibm.com", "time": "Mon Oct 30 22:07:20 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 31 08:07:01 2006 -0800" }, "message": "[PATCH] eCryptfs: Remove ecryptfs_umount_begin\n\nThere is no point to calling the lower umount_begin when the eCryptfs\numount_begin is called.\n\nSigned-off-by: Michael Halcrow \u003cmhalcrow@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "237fead619984cc48818fe12ee0ceada3f55b012", "tree": "40c6cacf2331191139e847988882b168d111c12e", "parents": [ "f7aa2638f288f4c67acdb55947472740bd27d27a" ], "author": { "name": "Michael Halcrow", "email": "mhalcrow@us.ibm.com", "time": "Wed Oct 04 02:16:22 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Wed Oct 04 07:55:24 2006 -0700" }, "message": "[PATCH] ecryptfs: fs/Makefile and fs/Kconfig\n\neCryptfs is a stacked cryptographic filesystem for Linux. It is derived from\nErez Zadok\u0027s Cryptfs, implemented through the FiST framework for generating\nstacked filesystems. eCryptfs extends Cryptfs to provide advanced key\nmanagement and policy features. eCryptfs stores cryptographic metadata in the\nheader of each file written, so that encrypted files can be copied between\nhosts; the file will be decryptable with the proper key, and there is no need\nto keep track of any additional information aside from what is already in the\nencrypted file itself.\n\n[akpm@osdl.org: updates for ongoing API changes]\n[bunk@stusta.de: cleanups]\n[akpm@osdl.org: alpha build fix]\n[akpm@osdl.org: cleanups]\n[tytso@mit.edu: inode-diet updates]\n[pbadari@us.ibm.com: generic_file_*_read/write() interface updates]\n[rdunlap@xenotime.net: printk format fixes]\n[akpm@osdl.org: make slab creation and teardown table-driven]\nSigned-off-by: Phillip Hellewell \u003cphillip@hellewell.homeip.net\u003e\nSigned-off-by: Michael Halcrow \u003cmhalcrow@us.ibm.com\u003e\nSigned-off-by: Erez Zadok \u003cezk@cs.sunysb.edu\u003e\nSigned-off-by: Adrian Bunk \u003cbunk@stusta.de\u003e\nSigned-off-by: Stephan Mueller \u003csmueller@chronox.de\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nSigned-off-by: Badari Pulavarty \u003cpbadari@us.ibm.com\u003e\nSigned-off-by: Randy Dunlap \u003crdunlap@xenotime.net\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" } ] }