From: Artem Bityutskiy <dedekind1@gmail.com>
To: Christoph Hellwig <hch@lst.de>,
viro@zeniv.linux.org.uk, joern@logfs.org,
prasadjoshi.linux@gmail.com
Cc: logfs@logfs.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] logfs: remove from tree
Date: Mon, 12 Sep 2016 09:55:01 +0300 [thread overview]
Message-ID: <1473663301.2342.442.camel@gmail.com> (raw)
In-Reply-To: <1473599062-23550-1-git-send-email-hch@lst.de>
On Sun, 2016-09-11 at 15:04 +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 <hch@lst.de>
Back in 2008 logfs and UBIFS were in sort of competing projects. I
remember we inspected logfs code and tested it - we did not find proper
wear-levelling and bad block handling, we did not see proper error
handling, and it exploded when we were running relatively simple tests.
We indicated this here in a very humble way to avoid the "conflict of
interest" perseption:
https://lkml.org/lkml/2008/3/31/117
I did not follow logfs since then, but I think there wasn't much
development since then and all these issue are still there. I mean,
unless I am horribly mistaken, logfs does not really have the basic
features of a flash file system and there is no point keeping it in the
tree and consuming people's time maintaining it.
Artem.
next prev parent reply other threads:[~2016-09-12 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 13:04 [PATCH] logfs: remove from tree Christoph Hellwig
2016-09-12 1:53 ` Dave Chinner
2016-09-12 5:11 ` Christoph Hellwig
2016-09-12 6:55 ` Artem Bityutskiy [this message]
2016-09-12 15:53 ` Austin S. Hemmelgarn
2016-10-15 0:33 ` Al Viro
2016-10-24 6:37 ` Christoph Hellwig
2016-12-01 10:06 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1473663301.2342.442.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=hch@lst.de \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logfs@logfs.org \
--cc=prasadjoshi.linux@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).