On Wed, Aug 15, 2018 at 09:46:13AM +0100, Filipe Manana wrote: > >> > I had in mind was some leftover from locking, error handling or state > >> > that blocked umount of 011. > >> > >> Dave, are you sending this in for 4.19? I don't see it in your first > >> pull request. > > In another thread, related to the first patch in the series iirc, I > specifically asked to not merge it.
Ah right, I remember now. Yesterday I only checked mails in the thread of the patch and the mail was marked as 'applied to some branch'. > That's because I run twice (in the long period of nearly 2 months now) > into a hang which could be caused > by this patch. The traces were weird and only contained inexact lines > that showed only the transaction kthread > waiting forever on transaction commit. > > I recently found that I have hardware problems that were causing > issues with qemu (stalls, ocassional crashes) > so I'm hoping that's the cause but I still need to test it with long > stress tests on good hardware. > > I don't mind getting it to linux-next in the meanwhile, but for 4.19 I > would prefer to not include yet. Ok, understood.
