[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] [PATCH 02/13] dm: kill dm_rq_bio_destructor
- From: Kent Overstreet <koverstreet google com>
- To: Tejun Heo <tj kernel org>, axboe kernel dk, dm-devel redhat com, linux-kernel vger kernel org, linux-bcache vger kernel org, linux-fsdevel vger kernel org, agk redhat com, Junichi Nomura <j-nomura ce jp nec com>, Mikulas Patocka <mpatocka redhat com>
- Subject: Re: [dm-devel] [PATCH 02/13] dm: kill dm_rq_bio_destructor
- Date: Fri, 18 May 2012 11:50:27 -0700
On Fri, May 18, 2012 at 05:43:19PM +0100, Alasdair G Kergon wrote:
> On Fri, May 18, 2012 at 08:57:29AM -0700, Tejun Heo wrote:
> > Please explain why this is done and how it's safe. Alasdair / dm
> > folks, can you please ack this?
>
> I think it's relying on there being never more than one reference on those
> bios so that that endio fn, called exactly once, always frees it and there
> are no dm_puts elsewhere.
Is that a safe assumption? From my perusal of the code it certainly
looks like it should be, but I don't know dm all that well.
Seems like it might be better to use bio set's front_pad to put it in
the same allocation as the bio, but I don't really want to get into that
myself.
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]