On Tuesday, November 14, 2017 10:25:38 PM CET Dave Chinner wrote: > On Tue, Nov 14, 2017 at 09:19:15PM +0100, Luis R. Rodriguez wrote: > > This is another way to say suspend has been busted on XFS for a very long time, > > but I would not blame XFS -- this is a kernel issue to get proper filesystem > > suspend working right, and the way we currently deal with kthreads is just > > a sloppy goo mess which has created this situation. > > Yes, and I've been telling people that suspend on journalling > filesystems has been broken for a long time (i.e since I first > realised the scope of the problem back in 2005). However, only XFS > triggers those conditions regularly because it is the most > asynchronous of the "freezable" journalling filesytems and has the > most reliance on co-ordination of kernel threads and workqueues to > function correctly. > > IOWs, suspend of filesystems has been broken forever, and we've been > slapping bandaids on it in XFS forever. Now we've got to a > catch-22 situation that bandaids can't fix. We need structural > fixes, like I said we needed to do more than 10 years ago. Right. Yet, apparently, nobody has had the time to make those changes for all that time. So what do you think should be done, specifically? Thanks, Rafael -- 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
