History log of /openbmc/linux/fs/cramfs/inode.c (Results 701 – 710 of 710)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v2.6.14-rc2
# d7f6884a 14-Sep-2005 Jeff Garzik <jgarzik@pobox.com>

Merge /spare/repo/linux-2.6/


Revision tags: v2.6.14-rc1
# d344c5e0 09-Sep-2005 Dmitry Torokhov <dtor_core@ameritech.net>

Manual merge with Linus


# 344a0761 08-Sep-2005 Tony Luck <tony.luck@intel.com>

[IA64] Manual merge fix for 3 files

arch/ia64/Kconfig
arch/ia64/kernel/acpi.c
include/asm-ia64/irq.h

Signed-off-by: Tony Luck <tony.luck@intel.com>


# 1d6ae775 08-Sep-2005 Jeff Garzik <jgarzik@pobox.com>

Merge /spare/repo/linux-2.6/


# 142e27fc 08-Sep-2005 Jeff Garzik <jgarzik@pobox.com>

Merge /spare/repo/linux-2.6/


# c324b44c 08-Sep-2005 Jeff Garzik <jgarzik@pobox.com>

Merge /spare/repo/linux-2.6/


# 5a2cec83 08-Sep-2005 Jeff Garzik <jgarzik@pobox.com>

Merge /spare/repo/linux-2.6/


# 64e47488 08-Sep-2005 Len Brown <len.brown@intel.com>

Merge linux-2.6 with linux-acpi-2.6


# a97c9bf3 06-Sep-2005 Dave Johnson <djohnson+linux-kernel@sw.starentnetworks.com>

[PATCH] fix cramfs making duplicate entries in inode cache

Every time cramfs_lookup() is called to lookup and inode for a dentry,
get_cramfs_inode() will allocate a new inode without checking to see

[PATCH] fix cramfs making duplicate entries in inode cache

Every time cramfs_lookup() is called to lookup and inode for a dentry,
get_cramfs_inode() will allocate a new inode without checking to see if that
inode already exists in the inode cache.

This is fine the first time, but if the dentry cache entry(ies) associated
with that inode are aged out, but the inode entry is not aged out (which can
be quite common if the inode has buffer cache linked to it), cramfs_lookup()
will be called again and another inode will be allocated and added to the
inode cache creating a duplicate in the inode cache.

The big issue here is that the buffers associated with each inode cache entry
are not shared between the duplicates!

The older inode entries are now orphaned as no dentry points to it and won't
be freed until the buffer cache assoicated with them are first freed. The
newest entry will have to create all new buffer cache for each part of its
file as the old buffer cache is now orphaned as well.

Patch below fixes this by making get_cramfs_inode() use the inode cache before
blindly creating a new entry every time. This eliminates the duplicate inodes
and duplicate buffer cache.

Cc: Phillip Lougher <phillip@lougher.demon.co.uk>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

show more ...


Revision tags: v2.6.13, v2.6.13-rc7, v2.6.13-rc6, v2.6.13-rc5, v2.6.13-rc4, v2.6.13-rc3, v2.6.13-rc2, v2.6.13-rc1, v2.6.12, v2.6.12-rc6, v2.6.12-rc5, v2.6.12-rc4, v2.6.12-rc3, v2.6.12-rc2
# 1da177e4 16-Apr-2005 Linus Torvalds <torvalds@ppc970.osdl.org>

Linux-2.6.12-rc2

Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in

Linux-2.6.12-rc2

Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!

show more ...


1...<<212223242526272829