From: Artem Bityutskiy <dedekind1@gmail.com>
To: Mark Jackson <mpfj-list@mimc.co.uk>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
adrian.hunter@intel.com
Subject: Re: MTD : Kernel oops when remounting ubifs as read/write
Date: Thu, 14 Mar 2013 14:18:49 +0200 [thread overview]
Message-ID: <1363263529.11441.109.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <5141BC63.6060501@mimc.co.uk>
On Thu, 2013-03-14 at 12:02 +0000, Mark Jackson wrote:
> But there's also a call to crc with a size of 122880 bytes, and that's
> when the oops occurs.
>
This is when we do the atomic LEB change.
> Is this size larger than the allocated buffer ?
I believe so.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-03-14 12:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 16:42 MTD : Kernel oops when remounting ubifs as read/write Mark Jackson
2013-03-12 11:25 ` Artem Bityutskiy
2013-03-13 11:12 ` Mark Jackson
2013-03-13 11:20 ` Artem Bityutskiy
2013-03-13 11:21 ` Mark Jackson
2013-03-14 9:13 ` Artem Bityutskiy
2013-03-14 9:54 ` Mark Jackson
2013-03-14 10:30 ` Artem Bityutskiy
2013-03-14 11:15 ` Mark Jackson
2013-03-14 11:23 ` Artem Bityutskiy
2013-03-14 12:02 ` Mark Jackson
2013-03-14 12:18 ` Artem Bityutskiy [this message]
2013-03-14 12:23 ` Artem Bityutskiy
2013-03-14 13:40 ` Mark Jackson
2013-03-14 13:55 ` Mark Jackson
2013-03-15 8:40 ` Artem Bityutskiy
2013-03-15 11:03 ` AM335x crc32 oops ? Mark Jackson
2013-03-15 8:42 ` MTD : Kernel oops when remounting ubifs as read/write Artem Bityutskiy
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=1363263529.11441.109.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpfj-list@mimc.co.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;
as well as URLs for NNTP newsgroup(s).