On 04/17/2016 06:44 PM, Sasha Levin wrote: > On 04/17/2016 02:37 PM, Christoph Hellwig wrote: >> > Adding Doug as this involves the SG driver, which has a slightly >> > unusual usage of the blk-map.c code. >> > >> > Does anyone know if the __asan_storeN in the trace implies the memory >> > stored to was invalid and not the memory read from? > Yes. In this case it attempted to write to memory that was already freed. Ping? I'm still seeing bunch of these in -next. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
