Re: [vfs-next] RCU call-traces (task: modprobe)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2022-08-06 at 20:48 +0200, Sedat Dilek wrote:
[...]
> Right now, I installed latest Debian-5.19 kernel to compare the Kconfig values:
> 
> [ Debian ]
> $ grep RCU /boot/config-5.19.0-trunk-amd64 | grep -i stall
> CONFIG_RCU_STALL_COMMON=y
> CONFIG_RCU_CPU_STALL_TIMEOUT=21
> CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=20
> 
> [ Sedat ]
> $ grep RCU /boot/config-5.19.0-2-amd64-clang15-kcfi | grep -i stall
> CONFIG_RCU_STALL_COMMON=y
> CONFIG_RCU_CPU_STALL_TIMEOUT=21
> CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=20
[...]

This is because of CONFIG_ANDROID changing the default for
CONFIG_RCU_EXP_CPU_STALL_TIMEOUT.  I'll cherry-pick the commits from
5.20 that remove that misfeature.

Ben.

-- 
Ben Hutchings
I haven't lost my mind; it's backed up on tape somewhere.

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux