From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Sean Nyekjaer <sean@geanix.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Richard Weinberger <richard@nod.at>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] PM / suspend: move userspace freeze before disk sync
Date: Fri, 3 Sep 2021 11:17:55 +0200 [thread overview]
Message-ID: <20210903111755.0972850d@xps13> (raw)
In-Reply-To: <20210903081751.3qq36nrksucqthss@skn-laptop>
Hi Sean,
sean@geanix.com wrote on Fri, 3 Sep 2021 10:17:51 +0200:
> On Thu, Sep 02, 2021 at 06:28:14PM +0200, Rafael J. Wysocki wrote:
> > On Wed, Sep 1, 2021 at 10:35 AM Sean Nyekjaer <sean@geanix.com> wrote:
> > >
> > > This fixes an issue where data remains unwritten before suspend.
> >
> > Well, it doesn't make the issue go away, it just hides it for you and
> > it may very well expose it for someone else.
>
> OK
>
> >
> > In particular, note that you can compile the kernel with
> > CONFIG_SUSPEND_SKIP_SYNC set which makes it not sync at all during
> > system-wide suspend and this is a valid case expected to work. It
> > looks like this case doesn't work for you.
> >
> > > UBI tried to write data, before the mtd device had been unsuspended.
> >
> > Well, that's the real problem and it can happen regardless of whether
> > or not this patch is there.
>
> How to fix it then?
> We can't live with devices that bricks on unsuspend :/
We then need to focus on UBI/UBIFS implementation (Richard is currently
off), maybe there is more logic than just a basic retry to implement.
Thanks,
Miquèl
prev parent reply other threads:[~2021-09-03 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 8:34 [PATCH] PM / suspend: move userspace freeze before disk sync Sean Nyekjaer
2021-09-02 16:28 ` Rafael J. Wysocki
2021-09-03 8:17 ` Sean Nyekjaer
2021-09-03 9:17 ` Miquel Raynal [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=20210903111755.0972850d@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
--cc=sean@geanix.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