On Sun, Sep 11, 2016 at 03:04:22PM +0200, Christoph Hellwig wrote: > Logfs was introduced to the kernel in 2009, and hasn't seen any non > drive-by changes since 2012, while having lots of unsolved issues > including the complete lack of error handling, with more and more > issues popping up without any fixes. > > The logfs.org domain has been bouncing from a mail, and the maintainer > on the non-logfs.org domain hasn't repsonded to past queries either. > > Signed-off-by: Christoph Hellwig <h...@lst.de> > --- > Documentation/filesystems/00-INDEX | 2 - > Documentation/filesystems/logfs.txt | 241 ---- > MAINTAINERS | 8 - > fs/Kconfig | 1 - > fs/Makefile | 1 - > fs/logfs/Kconfig | 17 - > fs/logfs/Makefile | 13 - > fs/logfs/compr.c | 95 -- > fs/logfs/dev_bdev.c | 322 ----- > fs/logfs/dev_mtd.c | 274 ----- > fs/logfs/dir.c | 797 ------------ > fs/logfs/file.c | 285 ----- > fs/logfs/gc.c | 732 ----------- > fs/logfs/inode.c | 428 ------- > fs/logfs/journal.c | 894 -------------- > fs/logfs/logfs.h | 735 ----------- > fs/logfs/logfs_abi.h | 629 ---------- > fs/logfs/readwrite.c | 2298 > ----------------------------------- > fs/logfs/segment.c | 961 --------------- > fs/logfs/super.c | 653 ----------
Wasn't the lib/btree.c implementation introduced with and only used by logfs? Should that go as well? Cheers, Dave. -- Dave Chinner da...@fromorbit.com
