On Fri, 2 Dec 2016, Dave Chinner wrote: > > Ultimately, the correct solution is to use filesystem freezing during > > suspend to quiesce the filesystem. However that requires more work on the > > suspend side - added Jiri to CC who promised to look into it some time ago > > ;). > > I've been saying that for 10 years, too, so I'm not going to hold my > breathe waiting for someone to fix this problem. Thanks for bringing up just another example why kthread freezer is such a mess. I already have a sort-of working implementation that gets rid of kthread freezer, but there is still quite some work to do before it's mainline ready. Namely, we first have to get rid of all of the spurious kthread freezer usage we have in the tree so far. The main part of this effort are these commits https://git.kernel.org/cgit/linux/kernel/git/jikos/jikos.git/commit/?h=might-rebase/get-rid-of-kthread-freezer&id=394aa67810abefde6d79ea96a90e5d41a7df99f4 https://git.kernel.org/cgit/linux/kernel/git/jikos/jikos.git/commit/?h=might-rebase/get-rid-of-kthread-freezer&id=3f0d7690cbf813ce497f2ca816d8086afe490271 https://git.kernel.org/cgit/linux/kernel/git/jikos/jikos.git/commit/?h=might-rebase/get-rid-of-kthread-freezer&id=a637de712f9ca60bea6e93b13d09534170ec29fa but especially the second commit needs a lot more care, as I am pretty sure it'd break some obscure corner cases, and needs to be investigated more. Also, NFS needs to be taught about fs freezing before we can proceed this way. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
