On 2024-06-20 02:37, Hailong Liu wrote: > On Thu, 20. Jun 02:19, Nick Bowler wrote: >> After upgrading my sparc to 6.9.5 I noticed that attempting to run >> xfsdump instantly (within a couple seconds) and reliably crashes the >> kernel. The same problem is also observed on 6.10-rc4. [...] >> 062eacf57ad91b5c272f89dc964fd6dd9715ea7d is the first bad commit >> commit 062eacf57ad91b5c272f89dc964fd6dd9715ea7d >> Author: Uladzislau Rezki (Sony) <urezki@xxxxxxxxx> >> Date: Thu Mar 30 21:06:38 2023 +0200 >> >> mm: vmalloc: remove a global vmap_blocks xarray [...] >> spitfire_data_access_exception: SFSR[000000000080100d] SFAR[0000000000c51ba0], going. >> \|/ ____ \|/ >> "@'/ .. \`@" >> /_| \__/ |_\ >> \__U_/ >> xfsdump(2028): Dax [#1] >> CPU: 0 PID: 2028 Comm: xfsdump Not tainted 6.9.5 #199 >> TSTATE: 0000000811001607 TPC: 0000000000974fc4 TNPC: 0000000000974fc8 Y: 00000000 Not tainted >> TPC: <queued_spin_lock_slowpath+0x1d0/0x2cc> [...] > I guess you can patch this > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?h=mm-hotfixes-unstable&id=00468d41c20cac748c2e4bfcf003283d554673f5 I tried with that patch applied on top of 6.10-rc4, and the crash still occurs. There is no obvious change in behaviour. Thanks, Nick
