On Sun, Oct 06, 2024 at 12:33:58PM +0530, Suraj Sonawane wrote: > > If it fails, then bio is initialized to NULL. > You're correct, bio_alloc_clone returns NULL if it fails, so there’s no > uninitialized bio after that. My initial explanation wasn’t fully accurate, > but initializing bio to NULL is just a safety measure for any unexpected > issues later on. Or i am just trying to solve this issue by smatch tool: > block/blk-mq.c:3199 blk_rq_prep_clone() error: uninitialized symbol 'bio'. Please do this kind of research and clearly state it in the commit log. Now the actual useful cleanup here would be to: - move the bio_put to the bio_ctr error handling, which is the only case where it can happen - move the bio variable into the __rq_for_each_bio scope, which also removed the need to zero it at the end of the loop That makes the easier to reason about, which should make whatever static checker you have happy, and also allows humans to read it more nicely.
