From: Richard Weinberger <richard@nod.at>
To: dedekind1@gmail.com
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: The future of ubi_assert()
Date: Thu, 06 Nov 2014 09:16:28 +0100 [thread overview]
Message-ID: <545B2E5C.7030809@nod.at> (raw)
In-Reply-To: <1415261634.958.175.camel@sauron.fi.intel.com>
Am 06.11.2014 um 09:13 schrieb Artem Bityutskiy:
> On Thu, 2014-11-06 at 09:07 +0100, Richard Weinberger wrote:
>> I think we can do better.
>> Think of wl.c, if an ubi_assert() in wl.c does not hold, we can put the UBI device
>> into read-only mode and continue execution.
>> BUG_ON() would be too much and WARN_ON() would lead to data corruption as the execution
>> would go on...
>> Something like ext4's errors=remount-ro. :)
>
> If you are willing to do the work, and if it is needed, and actually
> tested, sure.
Of course I will.
During fastmap development I ran into basically every ubi_assert() and
had to find out whether it is useful or not.^^
Thanks,
//richard
prev parent reply other threads:[~2014-11-06 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 22:02 The future of ubi_assert() Richard Weinberger
2014-11-06 7:21 ` Artem Bityutskiy
2014-11-06 8:07 ` Richard Weinberger
2014-11-06 8:13 ` Artem Bityutskiy
2014-11-06 8:16 ` Richard Weinberger [this message]
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=545B2E5C.7030809@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--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).