Regardless of how Kconfig options interact with each other, it seems that this 
bug is only triggered when the effective kernel config (/proc/config.gz) 
contains the following:

CONFIG_EXPERT=y
# CONFIG_UID16 is not set

Cheers,
Carl Dong


Reply via email to