Closed mudongliang closed 3 years ago
Sorry, what problem are you trying to solve by pushing this to KMSAN? Shouldn't this be fixed upstream instead?
KMSAN bugs can only be tested on https://github.com/google/kmsan.git tree because KMSAN tool is not upstreamed yet. See https://goo.gl/tpsmEJ#kmsan-bugs for details.
/\/\/\/\/\/\/\/\/\/\/\/\/\/\
Please see this link for how to test fixes for KMSAN bugs using syzbot. Or, of course, you can test locally as well.
I know this should be not the right place to post. However, I cannot test KMSAN-instrumented kernel locally as there is a massive amount of dmesg from KMSAN, which forbids the useful dmesg
My own fork of KMSAN cannot test with syzbot. So I try to push it to the google/kmsan
[1] https://syzkaller.appspot.com/bug?id=a84ac404cf07db753e289b918981964b540359bd