{"push_id":586418231,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"3d0e3417997d9caa27cf97462e15ba437d285d29","before":"de71b95eb99e07102b5059cac46c0d34bbfda907","commits":[{"sha":"3d0e3417997d9caa27cf97462e15ba437d285d29","author":{"email":"cd8c6775e60d6f67a6984377324e5290df3d5358@fb.com","name":"Jens Axboe"},"message":"Fix segfault due to bad munmap()\n\nBruce reports:\n\nThe latest code from git (built using clang) causes a segfault after printing the usage text when \"./fio\" is run:\n\n[New LWP 100111]\nNo jobs(s) defined\n\nfio-2.2.5-28-g93eeb\n[usage text]\n[New Thread 801c06400 (LWP 100111/fio)]\n\nProgram received signal SIGSEGV, Segmentation fault.\n[Switching to Thread 801c06400 (LWP 100111/fio)]\nflist_empty (head=0x802000040) at flist.h:119\n119             return head->next == head;\nCurrent language:  auto; currently minimal\n(gdb) p head\n$1 = (const struct flist_head *) 0x802000040\n\nwhich is due to a bug in the filelock code, that uses\nfio_mutex_remove() to remove the mutex. But that mutex is embedded\ninside another mmap'ed region, hence we then segfault on later\ndeferencing pointers.\n\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/axboe/fio/commits/3d0e3417997d9caa27cf97462e15ba437d285d29"}]}