On 25 April 2011 17:31, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > 2011/4/25 Bruno PrÃmont <bonbons@xxxxxxxxxxxxxxxxx>: >> kmemleak reports 86681 new leaks between shortly after boot and -2 state. >> (and 2348 additional ones between -2 and -4). > > I wouldn't necessarily trust kmemleak with the whole RCU-freeing > thing. In your slubinfo reports, the kmemleak data itself also tends > to overwhelm everything else - none of it looks unreasonable per se. Kmemleak reports that it couldn't find any pointers to those objects when scanning the memory. In theory, it is safe with RCU since objects queued for freeing via the RCU are in a linked list and still referred. There are of course false positives, usually when pointers are stored in some structures not scanned by kmemleak (e.g. some arrays allocated with alloc_pages which are not explicitly tracked by kmemleak) but I haven't seen any related to RCU (yet). -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
