lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bd0f97a1003031620s44cff658x81fc36fa2a8efd96@mail.gmail.com>
Date:	Wed, 3 Mar 2010 19:20:37 -0500
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Maxin John <maxin.john@...il.com>
Cc:	Arnd Bergmann <arnd@...db.de>, Peter Paul <abnominales@....de>,
	linux-kernel@...r.kernel.org
Subject: Re: yaffs2 NAND fs

On Wed, Mar 3, 2010 at 10:09, Maxin John wrote:
> On Tue, Mar 2, 2010 at 7:21 PM, Arnd Bergmann wrote:
>> On Tuesday 02 March 2010, Peter Paul wrote:
>>> I was wondering why the yaffs2 file system has not gone for mainline
>>> yet. It's rather popular flash file system in the embedded world, while
>>> it is rather easy to patch a kernel to have yaffs2 support [1] it would
>>> be even nicer if it was just in mainline.
>>> The source of the GPLv2 file system can be found at [2]
>>>
>>> [1] http://www.yaffs.net/howto-incorporate-yaffs
>>> [2] http://www.aleph1.co.uk/cgi-bin/viewcvs.cgi/yaffs2/
>>
>> I would guess it's a combination of multiple reasons:
>>
>> 1. It has not been submitted for upstream inclusion, at least not
>>   during the last few years.
>> 2. We don't have a staging area like drivers/staging for file systems
>>   in the way that we have for drivers
>> 3. There is now ubifs and (soon) logfs upstream, both of which appear
>>   to be superior to yaffs in many ways.
>
> This means there should be no reference to YAFFS2 in the upstream
> kernel? Because, I have located some defconfigs in upstream kernel
> where YAFFS2 support is enabled by default.

irrelevant noise
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ