From: Maurice Smulders <maurice.smulders@genevatech.net>
To: linux-mtd@lists.infradead.org
Subject: ubihealthd status
Date: Mon, 2 Nov 2020 12:20:13 -0700 [thread overview]
Message-ID: <CACxOKoJSoOMjeZncUV5Rae8+bbHgn-0viZmAZV2c0vP3+zRMGw@mail.gmail.com> (raw)
I am trying to determine how to be able to figure out if a PEB had an
uncorrectable bitflip and expose it to user space.
It would be good to determine if a specific volume is suspect
determined from the actual LEB, and have some exposure in for example
SYSFS. Would the actual volume be turned read-only?
I'm open to suggestions, either I build something into ubihealthd to
notify user programs to tell something bad has happened, or sysfs (but
that cannot notify)
The problem I have is that one of the apps i need to support this for
is commercial - and I couldn't change ubihealthd to a libary because
it is GPLv2, the other app is now Apache License based I think, it
used to be under NOSA. Also UBIHEALTHD doesn't necessarily have
access to which LEB/Volume is potentially affected.
-Maurice
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-11-02 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 19:20 Maurice Smulders [this message]
2020-11-02 22:06 ` ubihealthd status Richard Weinberger
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=CACxOKoJSoOMjeZncUV5Rae8+bbHgn-0viZmAZV2c0vP3+zRMGw@mail.gmail.com \
--to=maurice.smulders@genevatech.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).