Received-SPF: pass (google.com: domain of linux-kernel+bounces-43305-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 29 Jan 2024 18:18:00 +0000
From: a-development@posteo.de
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, peterz@infradead.org,
 David.Kaplan@amd.com, Andrew.Cooper3@citrix.com, jpoimboe@kernel.org,
 gregkh@linuxfoundation.org
Subject: Re: [RFC][PATCH 00/17] Fix up the recent SRSO patches
In-Reply-To: <20240127194139.GFZbVcc2RxhNtO3ZHD@fat_crate.local>
References: <cbad6acb30e33e8dd387080e5936cc38@posteo.net>
 <20240127191942.GEZbVXTtDNzLB9hTpr@fat_crate.local>
 <181005cf4a78a4c3c5e1de77498f6c23@posteo.net>
 <20240127194139.GFZbVcc2RxhNtO3ZHD@fat_crate.local>
Message-ID: <6170a3f60cd1ca68bca5829db4a8568a@posteo.net>

Hello.

I have the feeling that something else is amiss.
Currently under 6.7.2-2-cachyos with srso=off.
https://0x0.st/HDqP.txt

Now I feel, further communication is rather selfish, as a clean 
environment is hard to provide.
In any case, my FUSE arguments are sshfs -o kernel_cache -o auto_cache 
-o reconnect \
                -o compression=yes -o cache_timeout=600 -o 
ServerAliveInterval=30 \
                "$source" "$target" -o idmap=user

With this line, I somehow managed to have the FUSE mount infinitely 
mounted, even if the device was offline for couple of days.
A followed suspend would fail to freeze.
srso=off would reproducibly work.

Please provide me a specific version of a kernel I should try in my 
configuration to try and reproduce.
I'd prefer a pre-compiled one; if not tell me...
I use archlinux.

Please give me a reason to not feel bad about myself.

All the best


On 27.01.2024 20:41, Borislav Petkov wrote:
> On Sat, Jan 27, 2024 at 07:27:45PM +0000, a-development@posteo.de 
> wrote:
>> I can umount the FUSE mounts and it will work fine.
> 
> Aha, so it is FUSE-related.
> 
> How do I trigger it here? What are the steps to reproduce? Suspend 
> while
> I have a FUSE mount? How do I set it up so that it is as close to yours
> as possible?
> 
>> Previously I didn't even suspend.  Also, in the log I had provided,
>> I was on a cachyos kernel, but it didn't matter, even the most recent
>> arch kernel had the same issues.
> 
> You should try an upstream kernel to confirm it reproduces there - no
> distro kernels.
> 
>> full dmesg is no problem - I can do that the next day, when I startup
>> the server again full ~/.config folder I don't want to share
> 
> Not the full .config folder - just the kernel .config of the kernel
> you're triggering this with so that I can try to do it here too.
> 
>> here is /proc/cpuinfo https://paste.cachyos.org/p/158b767
> 
> Thx.