public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
	 "Rafael J. Wysocki" <rafael@kernel.org>,
	Pavel Machek <pavel@kernel.org>, Len Brown <len.brown@intel.com>,
	linux-pm@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] Filesystem Suspend Resume
Date: Fri, 21 Mar 2025 13:00:24 -0400	[thread overview]
Message-ID: <62bfd49bc06a58e435431610256e722651e1e5ca.camel@HansenPartnership.com> (raw)
In-Reply-To: <576418420308d2511a4c155cc57cf0b1420c273b.camel@HansenPartnership.com>

On Fri, 2025-03-21 at 08:34 -0400, James Bottomley wrote:
[...]
> Let me digest all that and see if we have more hope this time around.

OK, I think I've gone over it all.  The biggest problem with
resurrecting the patch was bugs in ext3, which isn't a problem now. 
Most of the suspend system has been rearchitected to separate
suspending user space processes from kernel ones.  The sync it
currently does occurs before even user processes are frozen.  I think
(as most of the original proposals did) that we just do freeze all
supers (using the reverse list) after user processes are frozen but
just before kernel threads are (this shouldn't perturb the image
allocation in hibernate, which was another source of bugs in xfs).

There's a final wrinkle in that if I plumb efivarfs into all this, it
needs to know whether it was a hibernate or suspend, but I can add that
as an extra freeze_holder flag.

This looked like such a tiny can of worms when I opened it; now it
seems to be a lot bigger on the inside than it was on the outside,
sigh.

Regards,

James


  reply	other threads:[~2025-03-21 17:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0a76e074ef262ca857c61175dd3d0dc06b67ec42.camel@HansenPartnership.com>
     [not found] ` <Z9xG2l8lm7ha3Pf2@infradead.org>
     [not found]   ` <acae7a99f8acb0ebf408bb6fc82ab53fb687559c.camel@HansenPartnership.com>
2025-03-21  5:23     ` [LSF/MM/BPF TOPIC] Filesystem Suspend Resume Christoph Hellwig
2025-03-21 12:34       ` James Bottomley
2025-03-21 17:00         ` James Bottomley [this message]
2025-03-21 17:17           ` Lukas Wunner
2025-03-21 18:20             ` James Bottomley
2025-03-24 11:38           ` [Lsf-pc] " Jan Kara
2025-03-24 14:34             ` James Bottomley
2025-03-24 19:28               ` Jan Kara
2025-03-27 14:55                 ` Eric Sandeen
2025-03-27 17:30                   ` Jan Kara
2025-03-24 20:56               ` Dave Chinner
2025-03-24 20:50             ` Dave Chinner
2025-03-24 21:02               ` James Bottomley
2025-03-24 21:07                 ` Dave Chinner
2025-03-25 13:42                   ` Jan Kara
2025-03-26  2:36                     ` James Bottomley
2025-03-26 14:59                       ` Jan Kara
2025-03-26 15:25                         ` James Bottomley
2025-03-27 14:28                           ` James Bottomley

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=62bfd49bc06a58e435431610256e722651e1e5ca.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=hch@infradead.org \
    --cc=len.brown@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.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