linux-kernel - Re: [PATCH v2 0/4] power: wire-up filesystem freeze/thaw with suspend/resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19873ac5902.f6db52da11419.248728138565404083@zohomail.com>
Date: Mon, 04 Aug 2025 10:02:11 +0400
From: Askar Safin <safinaskar@...omail.com>
To: "Miklos Szeredi" <miklos@...redi.hu>
Cc: "Jan Kara" <jack@...e.cz>, "brauner" <brauner@...nel.org>,
	"James.Bottomley" <James.Bottomley@...senpartnership.com>,
	"ardb" <ardb@...nel.org>, "boqun.feng" <boqun.feng@...il.com>,
	"david" <david@...morbit.com>, "djwong" <djwong@...nel.org>,
	"hch" <hch@...radead.org>, "linux-efi" <linux-efi@...r.kernel.org>,
	"linux-fsdevel" <linux-fsdevel@...r.kernel.org>,
	"linux-kernel" <linux-kernel@...r.kernel.org>,
	"mcgrof" <mcgrof@...nel.org>, "mingo" <mingo@...hat.com>,
	"pavel" <pavel@...nel.org>, "peterz" <peterz@...radead.org>,
	"rafael" <rafael@...nel.org>, "will" <will@...nel.org>,
	"Joanne Koong" <joannelkoong@...il.com>,
	"linux-pm" <linux-pm@...r.kernel.org>,
	"senozhatsky" <senozhatsky@...omium.org>
Subject: Re: [PATCH v2 0/4] power: wire-up filesystem freeze/thaw with
 suspend/resume

 ---- On Mon, 04 Aug 2025 09:31:00 +0400  Miklos Szeredi <miklos@...redi.hu> wrote --- 
 > This is a known problem with an unknown solution.
 > 
 > We can fix some of the cases, but changing all filesystem locks to be
 > freezable is likely not workable.

So what to do in case of networked FUSE, such as sshfs?
We should put workaround to other place?
Where? To libfuse or to each networked FUSE daemon, such as sshfs?
I hit this bug in the past, and I'm very angry.
A lot of other people hit this FUSE bug, too: https://github.com/systemd/systemd/issues/37590 .

What about this timeout solution: https://lore.kernel.org/linux-fsdevel/20250122215528.1270478-1-joannelkoong@gmail.com/ ?
Will it work? As well as I understand, currently kernel waits 20 seconds, when it tries to freeze processes when suspending.
So, what if we use this Joanne Koong's timeout patch, and set timeout to 19 seconds?

So, in short, if we cannot properly fix kernel, then where fix belongs? What should we do?
--
Askar Safin
https://types.pl/@safinaskar