You guys definitely want to know how to find more data race bugs using a fuzzer. Please check the talk from my labmate Meng Xu. He found 9 harmful race bugs in Linux using Krace.
Krace: Data Race Fuzzing for Kernel File Systems #SP20 #IEEESP
Video:https://www.youtube.com/watch?v=8m2fMxvRtgg …
-
Show this thread
-
The paper is here: https://cc.gatech.edu/~mxu80/pubs/xu:krace.pdf … BTW, the leader of this project, Meng Xu(https://cc.gatech.edu/~mxu80/ ), will be joining the University of Waterloo as an assistant professor in 2021. You can contact him for research opportunities in security, system, and program analysis.
1 reply 3 retweets 13 likesShow this thread -
-
Replying to @andreyknvl @hankein95
Do you deal with disjoined atomics and memory barriers? (E.g. wmb() + WRITE_ONCE() forms a happens-before relation with the matching READ_ONCE() + rmb().) We had some troubles with those in KTSAN.
1 reply 0 retweets 0 likes -
Replying to @andreyknvl @hankein95
No, we do not. I am curious to know how did you deal with those in KTSAN.
1 reply 0 retweets 0 likes -
Replying to @sanidhya_k @hankein95
You can find some details here:https://docs.google.com/presentation/d/1OsihHNut6E26ACTnT-GplQrdJuByRPNqUmN0HkqurIM/edit?usp=sharing …
1 reply 0 retweets 0 likes
(KTSAN is based on vector-clocks for happens-before tracking. All sync primitives and threads have clocks that are updated accordingly when synchronization happens. To deal with atomics and barriers we use additional "barrier" clocks.)
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.