Under /proc/sys/kernel there exists a parameters called kstack_depth_to_print. But I also see that a lot of other files (as listed below) not using this parameter directly from procfs.
Am I mistaken in my analysis?
./kernel/sysctl.c:
.procname = "kstack_depth_to_print",
.data = &kstack_depth_to_print,
./arch/m68k/kernel/traps.c:
static int kstack_depth_to_print = 48;
for (i = 0; i < kstack_depth_to_print; i++) {
./arch/m68knommu/kernel/traps.c:
int kstack_depth_to_print = 48;
for (i = 0; i < kstack_depth_to_print; i++) {
./arch/um/kernel/sysrq.c:
static const int kstack_depth_to_print = 24;
for (i = 0; i < kstack_depth_to_print; i++) {
./arch/blackfin/kernel/traps.c:
int kstack_depth_to_print = 48;
for (i = 0; i < kstack_depth_to_print; i++) {
./arch/x86/kernel/traps_64.c:
int kstack_depth_to_print = 12;
for(i=0; i < kstack_depth_to_print; i++) {
kstack_depth_to_print = simple_strtoul(s,NULL,0);
./arch/x86/kernel/traps_32.c:
int kstack_depth_to_print = 24;
for(i = 0; i < kstack_depth_to_print; i++) {
kstack_depth_to_print = simple_strtoul(s, NULL, 0);
./arch/m32r/kernel/traps.c:
int kstack_depth_to_print = 24;
for(i=0; i < kstack_depth_to_print; i++) {
./arch/powerpc/kernel/process.c:
static int kstack_depth_to_print = 64;
} while (count++ < kstack_depth_to_print);
./arch/h8300/kernel/traps.c:
static int kstack_depth_to_print = 24;
for (i = 0; i < kstack_depth_to_print; i++) {
./arch/xtensa/kernel/traps.c:
static int kstack_depth_to_print = 24;
for (i = 0; i < kstack_depth_to_print; i++) {
./arch/alpha/kernel/traps.c:
static int kstack_depth_to_print = 24;
for(i=0; i < kstack_depth_to_print; i++) {
./arch/s390/kernel/traps.c:
static int kstack_depth_to_print = 12;
static int kstack_depth_to_print = 20;
for (i = 0; i < kstack_depth_to_print; i++) {
./arch/cris/kernel/traps.c:
static int kstack_depth_to_print = 24;
for(i = 0; i < kstack_depth_to_print; i++) {
