Linux 5.18 To Try Again For x86/x86_64 "WERROR" Default

[phoronix]

Phoronix: Linux 5.18 To Try Again For x86/x86_64 "WERROR" Default

The Linux 5.18 merge window is ending today while sent in this morning were a batch of "x86/urgent" updates that include enabling the CONFIG_WERROR knob by default for Linux x86/x86_64 default configuration "defconfig" kernel builds...

https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.18-x86-WERROR

[JEBjames]

Michael

Hydrogen (h) is the most prevalent element in the universe?

But despite the article author's great wit, it can be mysteriously missing.

Typo: "wit" should be "with".

[milkylainen]

Linus won't accept anything but -Werror but is fine with the configs in disarray?
Something like 1k+ non-existent symbols in various defconfigs last time I checked.

[uid313]

What about switching from C11 to C17?

Or from gcc to cargo?

[NateHubbard]

Michael

Hydrogen (h) is the most prevalent element in the universe?

But despite the article author's great wit, it can be mysteriously missing.

Typo: "wit" should be "with".

I was a little more hung up on the "treated serious" line.

[EvilHowl]

What about switching from C11 to C17?

Or from gcc to cargo?

Yeah. Why bother fixing warnings when we can rewrite the whole kernel in Rust?

[JMB9]

Michael

Hydrogen (h) is the most prevalent element in the universe?

But despite the article author's great wit, it can be mysteriously missing.

Typo: "wit" should be "with".

Well, h is the Planck constant and the chemical symbol for hydrogen is H.
And seriously - "witH" looks even more strange than "wit", don't you think?
But maybe it is just a generation conflict - not using real digital devices without
touchpad but 'smart' devices may result in such mistakes without noticing ...
The normal world is case sensitive ... at least I hope so.
Additionally, this discussion is 2 days late ....

[RahulSundaram]

Yeah. Why bother fixing warnings when we can rewrite the whole kernel in Rust?

Rust usage in kernel still doesn't involve cargo. So the OP's comment doesn't make sense even then.

[WorBlux]

Linus won't accept anything but -Werror but is fine with the configs in disarray?
Something like 1k+ non-existent symbols in various defconfigs last time I checked.

WTF?

Are we talking symbols that show up on the config utility but no longer exist in the codebase, or the other way around?

Either way... ouch.

[milkylainen]

WTF?

Are we talking symbols that show up on the config utility but no longer exist in the codebase, or the other way around?

Either way... ouch.

Symbols that exist in various defconfigs that don't match up anywhere in the config system (indirectly code base), yes.
So it's not symbols that show up in a config utility. They need a description somewhere in the config system. Doesn't mean that they can't be wrong too.

It's more often symbols gone dead or not migrated properly.
Like CONFIG_SOMETHING_DRIVER used to work, but someone forgot to rename it to CONFIG_SOMETHING_NEW_DRIVER (namechange),
so it doesn't match anything in the descriptions anymore.
Some of them are just stupid mistakes. Others are like "wtf. I'm not sure some functionality has gone missing here..."

The three categories are a bit disjunct. They live their own life and rely mostly on manual handling to align them.
1. Symbols in the defconfigs (yes, partly manual, otherwise there wouldn't be so many dead symbols).
2. Symbols in code.
3. Symbols in the definition system (kconfig/lxdialog).

This is esp. painful for system maintainers.
But kernel developers usually don't care enough to inspect configuration migration mishaps between generations of the kernel.