public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, jack@suse.cz, rafael@kernel.org,
	Ard Biesheuvel <ardb@kernel.org>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	mcgrof@kernel.org, hch@infradead.org, david@fromorbit.com,
	djwong@kernel.org, pavel@kernel.org, mingo@redhat.com,
	will@kernel.org, boqun.feng@gmail.com
Subject: Re: [PATCH 0/6] power: wire-up filesystem freeze/thaw with suspend/resume
Date: Tue, 1 Apr 2025 16:59:17 +0200	[thread overview]
Message-ID: <20250401145917.GM5880@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250401-ballen-eulen-8d074cd8ca78@brauner>

On Tue, Apr 01, 2025 at 04:40:33PM +0200, Christian Brauner wrote:
> On Tue, Apr 01, 2025 at 04:14:07PM +0200, Peter Zijlstra wrote:
> > On Tue, Apr 01, 2025 at 02:32:45AM +0200, Christian Brauner wrote:
> > > The whole shebang can also be found at:
> > > https://web.git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git/log/?h=work.freeze
> > > 
> > > I know nothing about power or hibernation. I've tested it as best as I
> > > could. Works for me (TM).
> > > 
> > > I need to catch some actual sleep now...
> > > 
> > > ---
> > > 
> > > Now all the pieces are in place to actually allow the power subsystem to
> > > freeze/thaw filesystems during suspend/resume. Filesystems are only
> > > frozen and thawed if the power subsystem does actually own the freeze.
> > 
> > Urgh, I was relying on all kthreads to be freezable for live-patching:
> > 
> >   https://lkml.kernel.org/r/20250324134909.GA14718@noisy.programming.kicks-ass.net
> > 
> > So I understand the problem with freezing filesystems, but can't we
> > leave the TASK_FREEZABLE in the kthreads? The way I understand it, the
> 
> Yeah, we can.
> 
> > power subsystem will first freeze the filesystems before it goes freeze
> > threads anyway. So them remaining freezable should not affect anything,
> > right?
> 
> Yes. I've dropped the other patches. I've discussed this later
> downthread with Jan.

Thanks!

  reply	other threads:[~2025-04-01 14:59 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250329-work-freeze-v2-0-a47af37ecc3d@kernel.org>
2025-03-31 12:42 ` [PATCH 0/2] efivarfs: support freeze/thaw Christian Brauner
2025-03-31 12:42   ` [PATCH 1/2] libfs: export find_next_child() Christian Brauner
2025-03-31 12:42   ` [PATCH 2/2] efivarfs: support freeze/thaw Christian Brauner
2025-03-31 14:46     ` James Bottomley
2025-03-31 15:03       ` Christian Brauner
2025-04-01 19:31     ` James Bottomley
2025-04-02  7:44       ` Christian Brauner
2025-03-31 14:05   ` [PATCH 0/2] " Ard Biesheuvel
2025-04-01  0:32   ` [PATCH 0/6] power: wire-up filesystem freeze/thaw with suspend/resume Christian Brauner
2025-04-01  0:32     ` [PATCH 1/6] ext4: replace kthread freezing with auto fs freezing Christian Brauner
2025-04-01  9:16       ` Jan Kara
2025-04-01  9:35         ` Christian Brauner
2025-04-01 10:08           ` Jan Kara
2025-04-01  0:32     ` [PATCH 2/6] btrfs: " Christian Brauner
2025-04-01  0:32     ` [PATCH 3/6] xfs: " Christian Brauner
2025-04-01  1:11       ` Dave Chinner
2025-04-01  7:17         ` Christian Brauner
2025-04-01 11:35           ` Dave Chinner
2025-04-01 12:45             ` Christian Brauner
2025-04-01  0:32     ` [PATCH 4/6] fs: add owner of freeze/thaw Christian Brauner
2025-04-01  0:32     ` [PATCH 5/6] fs: allow pagefault based writers to be frozen Christian Brauner
2025-04-01  0:32     ` [PATCH 6/6] power: freeze filesystems during suspend/resume Christian Brauner
2025-04-01  8:16     ` [PATCH 0/6] power: wire-up filesystem freeze/thaw with suspend/resume Christian Brauner
2025-04-01  9:32     ` Jan Kara
2025-04-01 13:03       ` Christian Brauner
2025-04-01 16:57         ` Jan Kara
2025-04-02 14:07           ` [PATCH v2 0/4] " Christian Brauner
2025-04-02 14:07             ` [PATCH v2 1/4] fs: add owner of freeze/thaw Christian Brauner
2025-04-03 14:56               ` Jan Kara
2025-04-03 19:33                 ` Christian Brauner
2025-04-04 10:24                 ` [PATCH] fs: allow nesting with FREEZE_EXCL Christian Brauner
2025-04-07  9:08                   ` Christoph Hellwig
2025-05-07 11:18                   ` Jan Kara
2025-05-09 10:38                     ` Christian Brauner
2025-04-02 14:07             ` [PATCH v2 2/4] fs: allow all writers to be frozen Christian Brauner
2025-04-02 15:32               ` Christian Brauner
2025-04-02 16:03                 ` James Bottomley
2025-04-02 16:13                   ` Christian Brauner
2025-04-03 14:59               ` Jan Kara
2025-04-02 14:07             ` [PATCH v2 3/4] power: freeze filesystems during suspend/resume Christian Brauner
2025-04-03 16:29               ` Jan Kara
2025-04-02 14:07             ` [PATCH v2 4/4] kernfs: add warning about implementing freeze/thaw Christian Brauner
2025-04-03 15:00               ` Jan Kara
2025-07-20 19:23             ` [PATCH v2 0/4] power: wire-up filesystem freeze/thaw with suspend/resume Askar Safin
2025-07-21 12:09               ` Jan Kara
2025-08-04  5:31                 ` Miklos Szeredi
2025-08-04  6:02                   ` Askar Safin
2025-08-04  6:51                     ` Sergey Senozhatsky
2025-04-01 14:14     ` [PATCH 0/6] " Peter Zijlstra
2025-04-01 14:40       ` Christian Brauner
2025-04-01 14:59         ` Peter Zijlstra [this message]
2025-04-01 17:02     ` James Bottomley
2025-04-02  7:46       ` Christian Brauner
2025-04-08 15:43         ` James Bottomley
2025-04-08 17:09           ` Luis Chamberlain
2025-04-08 17:20             ` Luis Chamberlain
2025-04-08 17:26               ` James Bottomley
2025-04-08 17:24             ` James Bottomley
2025-04-09  7:17           ` Christian Brauner

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=20250401145917.GM5880@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=ardb@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=brauner@kernel.org \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mingo@redhat.com \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=will@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