Re: [PATCH v2 0/2] dm: Avoid use-after-free of a mapped device

2013-03-01 Thread Jun'ichi Nomura
On 02/28/13 22:00, Bart Van Assche wrote: How about reposting these patches as a performance optimization ? How and when do they improve performance? With these patches I see a slightly lower latency and slightly higher throughput. With a dm-linear mapping on top of a RAM disk (brd), a

Re: [PATCH v2 0/2] dm: Avoid use-after-free of a mapped device

2013-02-28 Thread Bart Van Assche
On 02/28/13 01:42, Jun'ichi Nomura wrote: Hi Bart, On 02/27/13 23:45, Bart Van Assche wrote: This mini-series of two patches avoids that the device mapper implementation can trigger a use-after-free during removal of a mapped device. The two patches in this series are: - block: Convert

[PATCH v2 0/2] dm: Avoid use-after-free of a mapped device

2013-02-27 Thread Bart Van Assche
This mini-series of two patches avoids that the device mapper implementation can trigger a use-after-free during removal of a mapped device. The two patches in this series are: - block: Convert blk_run_queue() recursion into iteration. - dm: Avoid running the md queue after the last dm_put().

Re: [PATCH v2 0/2] dm: Avoid use-after-free of a mapped device

2013-02-27 Thread Jun'ichi Nomura
Hi Bart, On 02/27/13 23:45, Bart Van Assche wrote: This mini-series of two patches avoids that the device mapper implementation can trigger a use-after-free during removal of a mapped device. The two patches in this series are: - block: Convert blk_run_queue() recursion into iteration. - dm: