Hi folks, These three patches are fixes for recent regressions. The first two are fixing up the mess that making the allocation workqueue kswapd aware. The first reverts the original patch, and the second moves the stack switch to the problematic double btree split path rather than being done for all writeback allocation. This allows the stack split to be done unconditionally for all allocations due to the relative rarity of it occurring now, and allows the kswapd awareness to be passed because we aren't going to swamp memory reclaim with hundreds of concurrent allocation requests from "kswapd" context. The last patch is for an older regression, and one that was tripped over recently when fixing up v3.2.0 of repair. It only affects people who are switching from newer kernels to older kernels and have only user quotas enabled. That combination shouldn't be too frequent - the fact the bug has been there since 3.12 indicates that this, indeed, isn't a frequent occurrence. Still, it needs to be fixed. Comments, thoughts, and testing all welcome... -Dave. _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
