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]
Date:	Wed, 3 Mar 2010 20:39:06 +0530
From:	Maxin John <maxin.john@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Peter Paul <abnominales@....de>, linux-kernel@...r.kernel.org
Subject: Re: yaffs2 NAND fs

Hi,

On Tue, Mar 2, 2010 at 7:21 PM, Arnd Bergmann <arnd@...db.de> 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.
ie:
CONFIG_YAFFS_YAFFS2=y
CONFIG_YAFFS_AUTO_YAFFS2=y
in below listed files:

1. arch/arm/configs/msm_defconfig
2. arch/blackfin/configs/IP0X_defconfig
3. arch/blackfin/configs/SRV1_defconfig
4. arch/blackfin/configs/BlackStamp_defconfig
5. arch/blackfin/configs/BF533-EZKIT_defconfig
6. arch/arm/configs/cam60_defconfig
7. arch/blackfin/configs/BF538-EZKIT_defconfig
8. arch/blackfin/configs/BF533-STAMP_defconfig
9. arch/blackfin/configs/PNAV-10_defconfig
10. arch/blackfin/configs/BF537-STAMP_defconfig
11. arch/blackfin/configs/BF526-EZBRD_defconfig
12. arch/blackfin/configs/BF527-EZKIT_defconfig,

Please let me know your opinion on this.

Best Regards,
Maxin B. John
--
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