From: Artem Bityutskiy <dedekind1@gmail.com>
To: Rick Johnson <rick22@wi.rr.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: read_pnode: error -22 reading pnode at XX:YYYYY
Date: Mon, 30 May 2011 19:07:58 +0300 [thread overview]
Message-ID: <1306771678.4405.25.camel@localhost> (raw)
In-Reply-To: <4DE00913.4060709@wi.rr.com>
On Fri, 2011-05-27 at 15:26 -0500, Rick Johnson wrote:
> I had some other observations that I might as well note too.
>
> We had added code to constantly check the value of pnode->num versus the
> num returned from calc_pnode_num_from_parent(). We noticed errors
> mainly in two places: ubifs_pack_pnode() and ubifs_get_pnode().
>
> The ubifs_get_pnode() was more interesting though. We only got a
> corrupted 'num' value when the function returned the pnode from memory
> and not from flash. In other words, when ubifs_get_pnode() followed
> this path:
>
> branch = &parent->nbranch[iip];
> pnode = branch->pnode;
> if (pnode)
> return pnode;
>
> So it seems like 'num' is getting corrupted or changed while the pnode
> is in memory. If it being corrupted in memory, it's strange that 'num'
> is so consistently targeted and that the corruption is not more random.
Well, there is some bug somewhere which corrupts memory, or this field,
I guess. I guess. I'd started putting more and more "targeted" checks at
different places and tried to narrow down the point when it gets
corrupted.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-05-30 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 21:08 read_pnode: error -22 reading pnode at XX:YYYYY Rick Johnson
2011-04-21 13:20 ` Artem Bityutskiy
2011-05-05 21:07 ` Rick Johnson
2011-05-06 18:32 ` Artem Bityutskiy
2011-05-09 17:41 ` Rick Johnson
2011-05-20 21:16 ` Rick Johnson
2011-05-24 8:41 ` Artem Bityutskiy
2011-05-24 11:43 ` Artem Bityutskiy
2011-05-27 20:26 ` Rick Johnson
2011-05-30 16:07 ` Artem Bityutskiy [this message]
2011-05-24 19:37 ` Rick Johnson
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=1306771678.4405.25.camel@localhost \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rick22@wi.rr.com \
/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).