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 for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1BDE6C83-889C-4E9A-9F92-C43BC50C529E@gmail.com>
Date: Wed, 18 Jun 2025 22:11:56 +0530
From: Abhigyan ghosh <zscript.team.zs@...il.com>
To: jhladky@...hat.com
CC: linux-kernel@...r.kernel.org
Subject: Re: Kernel panic in __migrate_swap_task() – more questions

Hello Jirka!,

Thank you so much for the detailed breakdown — this helps a lot.

Just a couple of quick follow-ups to better understand the environment:

1. Were you using Fedora's debug kernels (CONFIG_DEBUG_*, CONFIG_KASAN, etc.), or are these closer to production-style stripped builds?


2. For the crashing systems (especially the EPYC ones), did you observe any particular NUMA layout or memory pressure signs prior to the crash?


3. You mentioned repetition often triggered it — did you happen to try pinning stress-ng using --taskset or restricting cpusets to see if that changes the outcome?



I'll try reproducing locally by looping stress-ng --sem under perf to trace any irregularities.

Appreciate your time!

Best regards,
Abhigyan Ghosh
zscript.team.zs@...il.com
zsml.zscript.org
aghosh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ