Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disabling UBSAN due to instability on boot on some HW / module configurations #163

Merged
merged 1 commit into from Sep 5, 2021

Conversation

amoiseiev
Copy link
Contributor

@amoiseiev amoiseiev commented Sep 5, 2021

Addresses: #164

Problem statement:

Ubuntu's team decided to try and enable UBSAN on 5.14+ and 5.13.14+ builds, leading to boot issues on servers depending on modules used or hardware installed.

With hundreds of different kernel modules and thousands different configuration, this change in its current stage is high risk and questionable in general. These issues are impossible to predict and hard to troubleshoot. I believe it's worth disabling.

I reported it to Ubuntu kernel-team as well: https://lists.ubuntu.com/archives/kernel-team/2021-September/123828.html

@fabianishere fabianishere changed the base branch from master to v5.14.x September 5, 2021 09:10
The upstream Ubuntu kernel enables UBSAN on 5.14+ and 5.13.14+ builds, leading
to boot issues on servers depending on the hardware or module configuration.

With hundreds of different kernel modules and thousands different
configuration, this change in its current stage is high risk and questionable
in general.

These issues are impossible to predict and hard to troubleshoot.
Therefore, I believe it is worth disabling for now.

Resolves fabianishere#164
@fabianishere fabianishere added the bug Something isn't working label Sep 5, 2021
@fabianishere
Copy link
Owner

Thank you for your contribution!

I agree with your assessment (and it seems the people from Ubuntu do to). Funnily enough, one of my machines running v5.14 actually crashed today, so that might have something to do with it.

@fabianishere fabianishere merged commit 08f718b into fabianishere:v5.14.x Sep 5, 2021
fabianishere pushed a commit that referenced this pull request Sep 5, 2021
The upstream Ubuntu kernel enables UBSAN on 5.14+ and 5.13.14+ builds, leading
to boot issues on servers depending on the hardware or module configuration.

With hundreds of different kernel modules and thousands different
configuration, this change in its current stage is high risk and questionable
in general.

These issues are impossible to predict and hard to troubleshoot.
Therefore, I believe it is worth disabling for now.

Resolves #164
fabianishere added a commit that referenced this pull request Sep 5, 2021
The upstream Ubuntu kernel enables UBSAN on 5.14+ and 5.13.14+ builds, leading
to boot issues on servers depending on the hardware or module configuration.

With hundreds of different kernel modules and thousands different
configuration, this change in its current stage is high risk and questionable
in general.

These issues are impossible to predict and hard to troubleshoot.
Therefore, I believe it is worth disabling for now.

Resolves #164

Co-authored-by: Andrii Moiseiev <amoiseiev@gmail.com>
fabianishere pushed a commit that referenced this pull request Nov 10, 2021
The upstream Ubuntu kernel enables UBSAN on 5.14+ and 5.13.14+ builds, leading
to boot issues on servers depending on the hardware or module configuration.

With hundreds of different kernel modules and thousands different
configuration, this change in its current stage is high risk and questionable
in general.

These issues are impossible to predict and hard to troubleshoot.
Therefore, I believe it is worth disabling for now.

Resolves #164 and #200
fabianishere pushed a commit that referenced this pull request Nov 10, 2021
The upstream Ubuntu kernel enables UBSAN on 5.14+ and 5.13.14+ builds, leading
to boot issues on servers depending on the hardware or module configuration.

With hundreds of different kernel modules and thousands different
configuration, this change in its current stage is high risk and questionable
in general.

These issues are impossible to predict and hard to troubleshoot.
Therefore, I believe it is worth disabling for now.

Resolves #164 and #200
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants