On Mon, Jan 09, 2023 at 08:58:41PM -0800, Robert Dinse wrote:
>
> Increasing to 2048 did allow kernels to compile with KASAN enabled. I
> am curious why e-mail only? It would seem bugzilla, a public forum would
> make this fix available to others who may be experiencing the same or
> related problems.
Not all kernel developers pay attention to bugzilla. (In fact, most
kernel developers do not.)
> Interestingly, I could not locate the symbol with
> xconfig, had to hand edit the .config file in deference to the fact that it
> tells you not to.
If you search for FRAME_WARN in menuconfig ('/', followed by
"FRAME_WARN", followed by return), it will report:
Symbol: FRAME_WARN [=2048]
Type : integer
Range : [0 8192]
Defined at lib/Kconfig.debug:395
Prompt: Warn for stack frames larger than
Locationf
-> Kernel hacking
-> Compile-time checks and compiler options
(1) -> Warn for stack frames larger than (FRAME_WARN [=2048])
That being said, you can edit the .config file if you know what you
are doing. But if it breaks, you get to keep both pieces, since there
aren't the safety checks and guardrails of the supported paths. For
novices, I recommend saving a copy of .config before editing the
.config, and then afterwards, run "make oldconfig", and then diff the
resulting .config with the saved copy to make sure there aren't any
unexpected changes.
Cheers,
- Ted
