From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jean-Christophe DUBOIS <jcd@tribudubois.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [JFFS2] allow JFFS2 to discriminate between recoverable and non-recoverable errors
Date: Fri, 11 May 2012 20:05:33 +0300 [thread overview]
Message-ID: <1336755933.2625.100.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1336662824-2594-1-git-send-email-jcd@tribudubois.net>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
On Thu, 2012-05-10 at 17:13 +0200, Jean-Christophe DUBOIS wrote:
> This patch is basicaly a reverse of commit f326966b3df47f4fa7e90425f60efdd30c31fe19.
>
> It allows JFFS2 to make the distinction between a potential transient error
> (reading or writing the media) and a non recoverable error like a bad CRC on
> the extended attribute data or some insconsitent paramaters.
>
> In order to make clear that the error is indeed intended to report a corrupted
> attribute, a new local error code (JFFS2_XATTR_IS_CORRUPTED) is introduced.
>
> This error code is never reported to user space and only checked locally in this
> file.
Pushed both to l2-mtd.git, thanks!
Can you confirm that these 2 patches solve the issues you earlier
described on this mailing list?
--
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-05-11 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 15:13 [PATCH] [JFFS2] allow JFFS2 to discriminate between recoverable and non-recoverable errors Jean-Christophe DUBOIS
2012-05-11 17:05 ` Artem Bityutskiy [this message]
2012-05-16 8:19 ` Artem Bityutskiy
2012-05-16 8:28 ` Jean-Christophe DUBOIS
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=1336755933.2625.100.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=jcd@tribudubois.net \
--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).