From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
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: Thu, 20 Mar 2025 22:23:37 -0700 [thread overview]
Message-ID: <Z9z32X7k_eVLrYjR@infradead.org> (raw)
In-Reply-To: <acae7a99f8acb0ebf408bb6fc82ab53fb687559c.camel@HansenPartnership.com>
On Thu, Mar 20, 2025 at 02:15:15PM -0400, James Bottomley wrote:
> On Thu, 2025-03-20 at 09:48 -0700, Christoph Hellwig wrote:
> [...]
> > We finally got hibernate to freeze file system on suspend,
>
> I was looking for this to see if I could possibly plug something in for
> pseudo filesystems that don't have backing devices. However, I can't
> find the path where suspend causes freeze (at least the bdev doesn't
> seem to register any power notifier like the scsi block device does),
> where is the code?
Looking again I can't find it either. On the internet I find a patch
adding it from 2006:
https://groups.google.com/g/fa.linux.kernel/c/dtxsNJ7ks58/m/mqU8SIAbvLgJ
But I couldn't see if it got applied or disappaeared again somehow.
Adding the relevant maintainers.
next parent reply other threads:[~2025-03-21 5:23 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 ` Christoph Hellwig [this message]
2025-03-21 12:34 ` [LSF/MM/BPF TOPIC] Filesystem Suspend Resume James Bottomley
2025-03-21 17:00 ` James Bottomley
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=Z9z32X7k_eVLrYjR@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@hansenpartnership.com \
--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