On Tue, 2017-09-05 at 09:56 +0200, Paolo Valente wrote: > Ok, my suspects seem confirmed: the path dm_mq_queue_rq -> map_request > -> setup_clone -> blk_rq_prep_clone creates a cloned request without > invoking e->type->ops.mq.prepare_request for the target elevator e. > The cloned request is therefore not initialized for the scheduler, but > it is however inserted into the scheduler by > blk_mq_sched_insert_request. This seems an error for any scheduler > that needs to initialize fields in the incoming request, or in general > to take some preliminary action. > > Am I missing something here?
(+Mike Snitzer) Mike, do you perhaps have the time to look into this memory leak? Thanks, Bart.
