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

Issue in kernel what prevent using asan flags with gcc or clang #2105

Closed
4144 opened this Issue Aug 16, 2017 · 6 comments

Comments

Projects
None yet
2 participants
@4144

4144 commented Aug 16, 2017

Issue Report

Bug

In kernel 4.11.12 was added some changes what prevent working address sanitizer with gcc or clang.

for fix this issue already created patch here https://marc.info/?l=linux-kernel&m=150213695826001&w=2

Is possible to apply this patch to next coreos kernel update?

Container Linux Version

Detected this issue in CI and cant say exact version where bug was introduced, but can show good and bad closest kernel versions:

kernel without issue:

Linux runner-4e4528ca-project-180398-concurrent-0 4.11.11-coreos #1 SMP Tue Jul 18 23:06:59 UTC 2017 x86_64 GNU/Linux

kernel with issue:

Linux runner-4e4528ca-project-180398-concurrent-0 4.11.12-coreos-r1 #1 SMP Fri Aug 11 21:51:18 UTC 2017 x86_64 GNU/Linux

Environment

issue kernel related

Expected Behavior

Address sanitizers should works in any kernel

Other Information

Debian already patched own kernel with fix: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869090

More info about issue:

google/sanitizers#837

https://bbs.archlinux.org/viewtopic.php?pid=1729746

https://gitlab.com/gitlab-com/support-forum/issues/2350

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Aug 16, 2017

Member

The problem was introduced by coreos/linux@9b1bbf6. The next stable release is due shortly and will have a 4.12 kernel, but that will not fix the problem.

Member

bgilbert commented Aug 16, 2017

The problem was introduced by coreos/linux@9b1bbf6. The next stable release is due shortly and will have a 4.12 kernel, but that will not fix the problem.

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Aug 19, 2017

Member

The patch has been merged upstream as torvalds/linux@c715b72, but is not yet in the stable queue.

Member

bgilbert commented Aug 19, 2017

The patch has been merged upstream as torvalds/linux@c715b72, but is not yet in the stable queue.

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Aug 21, 2017

Member

Now in the 4.12 stable queue.

Member

bgilbert commented Aug 21, 2017

Now in the 4.12 stable queue.

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Aug 25, 2017

Member

Now in 4.12.9.

Member

bgilbert commented Aug 25, 2017

Now in 4.12.9.

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Aug 30, 2017

Member

Should be fixed in the next alpha release, 1520.0.0. Backported to the beta and stable channels but not yet scheduled into a release on those channels.

Member

bgilbert commented Aug 30, 2017

Should be fixed in the next alpha release, 1520.0.0. Backported to the beta and stable channels but not yet scheduled into a release on those channels.

@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Sep 5, 2017

Member

Should be fixed in beta 1492.6.0 and stable 1465.7.0, due shortly. Thanks for reporting.

Member

bgilbert commented Sep 5, 2017

Should be fixed in beta 1492.6.0 and stable 1465.7.0, due shortly. Thanks for reporting.

@bgilbert bgilbert closed this Sep 5, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment