public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 16 Apr 2024 06:48:54 +0000	[thread overview]
Message-ID: <d0dfa77ba8231652554c4e6088f985d1@posteo.net> (raw)
In-Reply-To: <20240326222134.GNZgNKbgdBUsAU98RV@fat_crate.local>

It worked, it worked!

https://up.tail.ws/txt/working-suspend.txt

I've tested it now quite some time.
But, I also had to start using 6.6.26-1-lts because my magewell capture 
card wouldn't without.

Thanks again!

On 26.03.2024 23:21, Borislav Petkov wrote:
> Whoops,
> 
> this fell through the cracks. Sorry about that.
> 
> On Mon, Jan 29, 2024 at 06:18:00PM +0000, a-development@posteo.de 
> wrote:
>> I have the feeling that something else is amiss.
>> Currently under 6.7.2-2-cachyos with srso=off.
>> https://0x0.st/HDqP.txt
> 
> Yah, your tasks refuse to freeze on suspend and they have this fuse
> stuff in the stacktrace:
> 
> [ 6346.492593] task:btop            state:D stack:0     pid:279617
> tgid:1548  ppid:1531   flags:0x00004006
> [ 6346.492600] Call Trace:
> [ 6346.492602]  <TASK>
> [ 6346.492607]  __schedule+0xd44/0x1af0
> [ 6346.492614]  ? srso_alias_return_thunk+0x5/0xfbef5
> [ 6346.492617]  ? __wake_up+0x9d/0xc0
> [ 6346.492622]  schedule+0x32/0xd0
> [ 6346.492627]  request_wait_answer+0xd0/0x2a0 [fuse
> db37c699d94393e946cf93306449ea0f307959a1]
> [ 6346.492638]  ? __pfx_autoremove_wake_function+0x10/0x10
> [ 6346.492643]  fuse_simple_request+0x21c/0x390 [fuse
> db37c699d94393e946cf93306449ea0f307959a1]
> [ 6346.492653]  fuse_statfs+0xf2/0x160 [fuse
> db37c699d94393e946cf93306449ea0f307959a1]
> [ 6346.492667]  statfs_by_dentry+0x67/0x90
> 
>> 
>> 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.
> 
> Not in your example above. It would fail after a couple of suspend
> cycles.
> 
> And looking at your splats
> 
> [ 6366.524953]  ? switch_fpu_return+0x50/0xe0
> [ 6366.524956]  ? srso_alias_return_thunk+0x5/0xfbef5
> 		  ^^^^^^^^^^^^^^^^^^^^^^^^
> [ 6366.524958]  ? exit_to_user_mode_prepare+0x132/0x1f
> 
> the right cmdline option to disable it is:
> 
> spec_rstack_overflow=off
> 
> not
> 
> srso=off
> 
> :-)
> 
>> 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.
> 
> Just build the latest released kernel, which is 6.8 now. Take your
> .config and use it to build it. The net is full of tutorials how to do
> so.
> 
> And then try with spec_rstack_overflow=off and let's see what that 
> does.
> 
>> Please give me a reason to not feel bad about myself.
> 
> Don't worry - it's just a machine. :)

  reply	other threads:[~2024-04-16  6:58 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
2024-03-26 22:21         ` Borislav Petkov
2024-04-16  6:48           ` a-development [this message]
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=d0dfa77ba8231652554c4e6088f985d1@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