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
Date: Mon, 29 Jan 2024 18:18:00 +0000 [thread overview]
Message-ID: <6170a3f60cd1ca68bca5829db4a8568a@posteo.net> (raw)
In-Reply-To: <20240127194139.GFZbVcc2RxhNtO3ZHD@fat_crate.local>
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.
next prev parent reply other threads:[~2024-01-29 18:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 18:58 [RFC][PATCH 00/17] Fix up the recent SRSO patches a-development
2024-01-27 19:19 ` Borislav Petkov
2024-01-27 19:27 ` a-development
2024-01-27 19:41 ` Borislav Petkov
2024-01-29 18:18 ` a-development [this message]
2024-03-26 22:21 ` Borislav Petkov
2024-04-16 6:48 ` a-development
2024-04-16 8:45 ` Borislav Petkov
2024-04-16 20:14 ` a-development
2024-04-17 8:08 ` a-development
2024-04-17 9:12 ` Borislav Petkov
2024-04-22 7:01 ` a-development
2024-01-27 19:28 ` a-development
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 7:12 Peter Zijlstra
2023-08-09 9:04 ` Nikolay Borisov
2023-08-09 10:04 ` Andrew.Cooper3
2023-08-09 11:58 ` Peter Zijlstra
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=6170a3f60cd1ca68bca5829db4a8568a@posteo.net \
--to=a-development@posteo.de \
--cc=Andrew.Cooper3@citrix.com \
--cc=David.Kaplan@amd.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@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