linux-kernel - Re: yaffs2 NAND fs

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] [day] [month] [year] [list]

Message-Id: <201003041443.14780.arnd@arndb.de>
Date:	Thu, 4 Mar 2010 14:43:14 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Wookey <wookey@...kware.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: yaffs2 NAND fs

On Thursday 04 March 2010, Wookey wrote:
> So, I guess this is another kick. I'll update the mainline patch I
> have (which is essentially just YAFFS2 with all the "#ifdef kernel
> nnn" code taken out, and the YAFFS-direct and ecos and WinCE code
> removed, to current kernel (which also means updating balloon3 to current
> kernel so I can actually test it). I'll put that in git and ask people
> to take a look. Detailed suggestions on what extra info is needed or
> changes made would be very helpful.
> 
> Unless of course there is already concensus that this is a waste of
> time and Peter and I are the only people that want to see it in
> mainline?

The bar for getting stuff into the kernel has gotten a lot lower these
days, at least for the staging part, see
http://www.kroah.com/log/linux/linux-staging-update.html

The basic requirement would be that you can get a patch that adds
a populated drivers/staging/yaffs2 directory actually builds, ideally
even mounts existing file sytem images without crashing every time ;-)

>From there, you can do all the cleanups that are necessary to
get it moved to fs/yaffs2, including the stuff you mention above
and whatever else comes up (put it into drivers/staging/yaffs2/TODO).

	Arnd
--
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/