Re: kmemcheck caught read from freed memory (cfq_free_io_context)

From: Fabio Checconi
Date: Wed Apr 02 2008 - 08:53:56 EST


> From: Jens Axboe <jens.axboe@xxxxxxxxxx>
> Date: Wed, Apr 02, 2008 02:36:39PM +0200
>
> > Looks good and tests fine as well. I've applied it, on top of the
> > hlist_for_each_entry_safe_rcu() fix.
> >
> > http://git.kernel.dk/?p=linux-2.6-block.git;a=commit;h=436151ad32b4a59e0d36165a7d6312545f126661
> >

ok, thanks. anyway I don't think the hlist_for_each_entry_safe_rcu()
is needed at this point, since the pos->next pointer is still valid
(at least) until the next rcu_read_unlock(). am I wrong?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/