I wrote a post: "Case study: Searching for a vulnerability pattern in the Linux kernel".
It's a funny story about #syzkaller, @Semmle @LGTM, Coccinelle and a "public 0day".https://a13xp0p0v.github.io/2019/08/10/cfu.html …
yeah, clang actually has address space numbers intended for segment-based addressing, but IIRC if you try to actually build a clang x86 kernel with address_space attributes, stuff blows up in the kernel's percpu accessors
-
-
tools/clang/docs/LanguageExtensions.rst says that the GS segment is address space 256 and the FS segment is address space 257, so it should be possible to define __percpu to be __attribute__((address_space(...))) in the kernel's compiler header.
-
But clang doesn't seem to have a way to write something like "__attribute__((address_space(0))) typeof(blah)" where "blah" has a type with a different explicit address space (it errors out because of the conflicting address spaces), and some stuff like that.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.