From: Richard Weinberger <richard@nod.at>
To: Hou Tao <houtao1@huawei.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Boris Brezillon <bbrezillon@kernel.org>,
dilinger@queued.net, linux-kernel <linux-kernel@vger.kernel.org>,
daniel santos <daniel.santos@pobox.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] jffs2:freely allocate memory when parameters are invalid
Date: Sat, 21 Sep 2019 17:37:35 +0200 (CEST) [thread overview]
Message-ID: <1837147225.3667.1569080255850.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <b2425bd2-38e9-cb9b-4151-94891f3a71d1@huawei.com>
Tao,
----- Ursprüngliche Mail -----
> Von: "Hou Tao" <houtao1@huawei.com>
> In Huawei we use jffs2 broadly in our products to support filesystem on raw
> NOR flash and NAND flash, so fixing the bugs in jffs2 means a lot to us.
>
> Although I have not read all of jffs2 code thoroughly, I had find and "fixed"
> some bugs in jffs2 and I am willing to do any help in the jffs2 community. Maybe
> we can start by testing and reviewing the pending patches in patch work ?
yes, this is a good idea.
In MTD's patchwork the jffs2 queue is in bad shape. I tried to catch up
but failed to find enough time. So with more eyeballs I think we can bring it
in shape again.
Basically we need to classify which patches fix important stuff and which do not.
Some time ago I make xfstests work with jffs2, I can share (and upstream) these
patches too.
One of my goals is making sure that we don't break jffs2. xfstests can help.
Are you on the OFTC IRC network? On #mtd you can find us MTD guys.
Thanks,
//richard
next prev parent reply other threads:[~2019-09-21 15:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 6:54 Xiaoming Ni
2019-09-20 11:43 ` Al Viro
2019-09-20 12:21 ` Xiaoming Ni
2019-09-20 12:45 ` Al Viro
2019-09-20 12:54 ` Al Viro
2019-09-20 14:13 ` Xiaoming Ni
2019-09-20 14:38 ` Richard Weinberger
2019-09-21 1:24 ` Hou Tao
2019-09-21 15:37 ` Richard Weinberger [this message]
2019-09-20 15:28 ` Al Viro
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=1837147225.3667.1569080255850.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=bbrezillon@kernel.org \
--cc=daniel.santos@pobox.com \
--cc=dilinger@queued.net \
--cc=dwmw2@infradead.org \
--cc=houtao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nixiaoming@huawei.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
Powered by JetHome