Joern Engel 6be7fa06eb [LogFS] Erase new journal segments ... If the device contains on old logfs image and the journal is moved to segment that have never been used by the current logfs and not all journal segments are erased before the next mount, the old content can confuse mount code. To prevent this, always erase the new journal segments. Signed-off-by: Joern Engel <joern@logfs.org>		2010-03-29 21:14:52 +02:00
..
Kconfig	…
Makefile	…
compr.c	…
dev_bdev.c	Plug memory leak in writeseg_end_io	2010-03-27 11:19:14 +01:00
dev_mtd.c	[LogFS] Fix bdev erases	2010-03-04 21:30:58 +01:00
dir.c	Prevent schedule while atomic in __logfs_readdir	2010-03-27 11:19:15 +01:00
file.c	…
gc.c	[LogFS] Only write journal if dirty	2010-03-04 21:36:19 +01:00
inode.c	Merge git://git.kernel.org/pub/scm/linux/kernel/git/joern/logfs	2010-03-06 13:18:03 -08:00
journal.c	[LogFS] Erase new journal segments	2010-03-29 21:14:52 +02:00
logfs.h	[LogFS] Clear PagePrivate when moving journal	2010-03-28 18:10:07 +02:00
logfs_abi.h	[LogFS] Change magic number	2010-03-06 10:03:11 +01:00
readwrite.c	Prevent data corruption in logfs_rewrite_block()	2010-03-28 12:40:42 +02:00
segment.c	[LogFS] Clear PagePrivate when moving journal	2010-03-28 18:10:07 +02:00
super.c	Use deactivate_locked_super	2010-03-27 11:19:16 +01:00