On Nov 3, 2014 6:27 PM, "Mikulas Patocka" <<a href="mailto:mpatocka@redhat.com">mpatocka@redhat.com</a>> wrote: > > > > On Tue, 28 Oct 2014, Mike Snitzer wrote: > > > I pushed rebased versions of these patches to linux-dm.git's > > 'dm-for-3.19' branch (and pulled into 'for-next' purely to get the > > <a href="http://kernel.org">kernel.org</a> autobuilders testing the code). See top 3 commits here: > > <a href="https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-for-3.19">https://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/log/?h=dm-for-3.19</a> > > > > I'm open to any and all changes or dropping code entirely; so me staging > > like this is just to keep the review ball rolling as quickly as > > possible. > > > > But in particular we need to get Mikulas' and Bryn's feedback on how the > > dm_internal_{suspend,resume} changes impact dm-stats. > > > > Mike > > Hi > > As I said on irc - it is not correct to take a mutex from one syscall and > drop the mutex from another syscall. I didn't modify that aspect of dm_internal_suspend+resume. I only extended the interface to other targets via export. > I hope Joe can use the bio prison to block bios while the pool is > suspended. We'll see.