linux-dev - Linux kernel development work

Age	Commit message (Collapse)	Author	Files	Lines
2006-01-09	[PATCH] mutex subsystem, semaphore to mutex: VFS, ->i_sem	Jes Sorensen	1	-4/+4
	This patch converts the inode semaphore to a mutex. I have tested it on XFS and compiled as much as one can consider on an ia64. Anyway your luck with it might be different. Modified-by: Ingo Molnar <mingo@elte.hu> (finished the conversion) Signed-off-by: Jes Sorensen <jes@sgi.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
2005-09-08	NTFS: Report unrepresentable inodes during ntfs_readdir() as KERN_WARNING	Anton Altaparmakov	1	-1/+2
	messages and include the inode number. Thanks to Yura Pakhuchiy for pointing this out. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
2005-06-25	NTFS: Fix several occurences of a bug where we would perform 'var & ~const'	Anton Altaparmakov	1	-1/+2
	with a 64-bit variable and a int, i.e. 32-bit, constant. This causes the higher order 32-bits of the 64-bit variable to be zeroed. To fix this cast the 'const' to the same 64-bit type as 'var'. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
2005-05-05	NTFS: Remove checks for NULL before calling kfree() since kfree() does the	Jesper Juhl	1	-8/+4
	checking itself. (Jesper Juhl) Signed-off-by: Jesper Juhl <juhl-lkml@dif.dk> Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
2005-05-05	NTFS: - Add disable_sparse mount option together with a per volume sparse	Anton Altaparmakov	1	-2/+2
	enable bit which is set appropriately and a per inode sparse disable bit which is preset on some system file inodes as appropriate. - Enforce that sparse support is disabled on NTFS volumes pre 3.0. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
2005-05-05	NTFS: In fs/ntfs/dir.c, use i_size_read() once and then the cached value	Anton Altaparmakov	1	-6/+7
	afterwards. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
2005-04-16	Linux-2.6.12-rc2	Linus Torvalds	1	-0/+1569
	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!