All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@sigma-star.at>
To: Kees Trommel <ctrommel@aimvalley.nl>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs robustness with early power cut warning
Date: Tue, 03 Oct 2017 09:26:29 +0200	[thread overview]
Message-ID: <1964048.Gvr1Jm0yVx@blindfold> (raw)
In-Reply-To: <7b89bbfe-8503-a50a-0271-09d69a99eeec@aimvalley.nl>

Am Dienstag, 3. Oktober 2017, 08:53:13 CEST schrieb Kees Trommel:
> Richard,
> 
> > Out of curiosity, did you also try to freeze or schedule the calling task?
> 
> No I did not. When the GPIO gets active the board will die (power off) so no
> need to freeze/block the calling task because it soon will die too. 

I just wondered whether the calling task does not do something stupid after 
being flooded with -EPERM upon every filesystem access.
Think of a larger software stack that communicates over a bus with other 
systems.

Thanks,
//richard

-- 
sigma star gmbh - Eduard-Bodem-Gasse 6 - 6020 Innsbruck - Austria
ATU66964118 - FN 374287y

      parent reply	other threads:[~2017-10-03  7:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 23:20 ubifs robustness with early power cut warning Doug Crawford
2017-09-30 16:19 ` Richard Weinberger
2017-10-02 16:14   ` Doug Crawford
2017-10-02 16:45     ` Richard Weinberger
2017-10-02 17:33       ` Doug Crawford
2017-10-02 18:03         ` Richard Weinberger
2017-10-02  8:06 ` Kees Trommel
2017-10-02 11:35   ` Richard Weinberger
2017-10-03  6:57     ` Kees Trommel
     [not found]     ` <7b89bbfe-8503-a50a-0271-09d69a99eeec@aimvalley.nl>
2017-10-03  7:26       ` 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=1964048.Gvr1Jm0yVx@blindfold \
    --to=richard@sigma-star.at \
    --cc=ctrommel@aimvalley.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.