From: Orjan Friberg <of@flatfrog.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: CONFIG_PREEMPT and JFFS2 oops
Date: Thu, 26 Jan 2012 12:54:00 +0100 [thread overview]
Message-ID: <4F213ED8.2020500@flatfrog.com> (raw)
In-Reply-To: <4F2127B8.9000005@flatfrog.com>
On 01/26/2012 11:15 AM, Orjan Friberg wrote:
>> problem to mysteriously disappear. Doing this analysis should provide a
>> good clue as to where to look next. I personally would be rather
>> suspicious of that
>>
>> ri->data_crc = cpu_to_je32(crc32(0, comprbuf, cdatalen));
>>
>> in jffs2_write_inode_range().
>
> That is indeed the place where crc32 is called from . I'll see it I can
> track the use of comprbuf.
Ok, so comprbuf comes from jffs2_compress and becomes NULL for some
reason (hence the oops).
Initially I had CMODE_FAVOUR_LZO. With that, things only worked with
PREEMPT_NONE. However, when changing to CMODE_PRIORITY or CMODE_NONE
things do seem to work *with* PREEMPT.
For what it's worth (with PREEMPT on):
CMODE_FAVOUR_LZO with LZO disabled oopses.
CMODE_FAVOUR_LZO with only ZLIB enabled oopses.
CMODE_FAVOUR_LZO with ZLIB/LZO/RTIME/RUBIN disabled does not oops.
Thus, the bug seems to be in the *selection* of compression algorithm
(when there is at least one algoritm in the list), rather than in the
specific compression algorithms themselves.
--
Orjan Friberg
FlatFrog Laboratories AB
next prev parent reply other threads:[~2012-01-26 11:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F206213.9070704@flatfrog.com>
[not found] ` <alpine.DEB.2.00.1201251351500.5324@utopia.booyaka.com>
2012-01-26 10:15 ` CONFIG_PREEMPT and JFFS2 oops Orjan Friberg
2012-01-26 11:19 ` Joakim Tjernlund
2012-01-26 11:54 ` Orjan Friberg [this message]
2012-01-26 16:09 ` Paul Walmsley
2012-01-26 16:28 ` Joakim Tjernlund
2012-01-26 16:35 ` Paul Walmsley
2012-01-26 16:38 ` Paul Walmsley
2012-01-26 16:48 ` Joakim Tjernlund
2012-01-26 16:57 ` Paul Walmsley
2012-01-26 17:33 ` Joakim Tjernlund
2012-01-26 20:01 ` Joakim Tjernlund
2012-01-28 9:51 ` Paul Walmsley
2012-01-28 14:42 ` Joakim Tjernlund
2012-01-28 9:50 ` Paul Walmsley
2012-01-26 17:54 ` Orjan Friberg
2012-01-26 16:37 ` Orjan Friberg
2012-01-26 16:43 ` Paul Walmsley
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=4F213ED8.2020500@flatfrog.com \
--to=of@flatfrog.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.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