Fiasco.OC: null-pointer dereference?

Leslie Zhai lesliezhai at llvm.org.cn
Thu Jun 8 04:18:00 CEST 2017


Hi Matthias,

Thank you so much for your pretty cool 
0001-Fix-invalid-initialization-in-new.patch 
http://os.inf.tu-dresden.de/pipermail/l4-hackers/2017/008005.html

Jean taught me about how to debug L4Re using jdb in qemu 
http://os.inf.tu-dresden.de/pipermail/l4-hackers/2017/008038.html it 
used a on purpose bug (null ptr deref) to crash Ned, then L4Re thrown: 
unhandled write page fault at 0x0 pc=0x100398d, and addr2line ... -e ned 
-a 100398d to indicate the root cause line.

But how to find out the root cause if unclear that which components 
bring in the issue? just like Jean investigated why 
framebuffer-example-x86 failed to work, actually it is not init process 
issue, but Fiasco `_quota` member of a thread is not correctly 
initialized. 0001-Fix-invalid-initialization-in-new.patch is awesome! 
how to debug deepinto it? it might be easy to a maintainer of Fiasco 
kernel, but it is really magic to me :)

The same story is how to debug L4Linux? 
http://os.inf.tu-dresden.de/pipermail/l4-hackers/2017/008047.html please 
give me some advice, thanks a lot!

-- 
Regards,
Leslie Zhai - a LLVM hacker https://reviews.llvm.org/p/xiangzhai/






More information about the l4-hackers mailing list