From: Artem Bityutskiy <dedekind1@gmail.com>
To: Andres Salomon <dilinger@queued.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] jffs2: implement mount option parsing and compression overriding
Date: Wed, 19 Oct 2011 17:22:28 +0300 [thread overview]
Message-ID: <1319034155.25389.81.camel@sauron> (raw)
In-Reply-To: <20111016181516.489cbbf9@queued.net>
On Sun, 2011-10-16 at 18:15 -0700, Andres Salomon wrote:
> Currently jffs2 has compile-time constants (and .config options)
> controlling whether or not the various compression/decompression
> drivers are built in and enabled. This is fine for embedded
> systems, but it clashes with distribution kernels. Distro kernels
> tend to turn on everything; this causes OpenFirmware to fall
> over, as it understands ZLIB-compressed inodes. Booting a kernel
> that has LZO compression enabled, writing to the boot partition,
> and then rebooting causes OFW to fail to read the kernel from
> the filesystem. This is because LZO compression has priority
> when writing new data to jffs2, if LZO is enabled.
>
> This patch adds mount option parsing, and a single supported
> option ("compr=none"). This adds the flexibility of being
> able to specify which compressor overrides on a per-superblock
> basis. For now, we can simply disable compression;
> additional flexibility coming soon.
Pushed both to l2-mtd-2.6.git, thanks!
--
Best Regards,
Artem Bityutskiy
prev parent reply other threads:[~2011-10-19 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 1:15 [PATCH v2 1/2] jffs2: implement mount option parsing and compression overriding Andres Salomon
2011-10-19 14:22 ` Artem Bityutskiy [this message]
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=1319034155.25389.81.camel@sauron \
--to=dedekind1@gmail.com \
--cc=dilinger@queued.net \
--cc=dwmw2@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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).