From: Artem Bityutskiy <dedekind1@gmail.com>
To: Reginald Perrin <reggyperrin@yahoo.com>
Cc: MTD Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: Help needed with corruption detection/ubifs_wbuf_sync_nolock
Date: Wed, 27 Jun 2012 17:23:14 +0300 [thread overview]
Message-ID: <1340806994.3070.34.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1340635736.72938.YahooMailNeo@web114615.mail.gq1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
On Mon, 2012-06-25 at 07:48 -0700, Reginald Perrin wrote:
> Update:
>
> I'm now doing this, and it seems to work. Is this correct?
>
> if ( wbuf->dtype != UBI_UNKNOWN && ((struct ubifs_ch *)wbuf->buf)->node_type > UBIFS_ORPH_NODE )
I do not think so, wbuf->buf points to a random byte, not to the
beginning of a node.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-27 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 13:58 Help needed with corruption detection/ubifs_wbuf_sync_nolock Reginald Perrin
2012-06-25 14:48 ` Reginald Perrin
2012-06-27 14:23 ` Artem Bityutskiy [this message]
2012-06-27 14:22 ` Artem Bityutskiy
2012-06-29 13:40 ` Reginald Perrin
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=1340806994.3070.34.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=reggyperrin@yahoo.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