On Sat, May 22, 2010 at 11:25:18AM -0500, Eric Sandeen wrote: > Michael Monnerie reported this fantastic stack overflow: > I don't think we can afford to let write_begin recurse into the fs, > so we can set AOP_FLAG_NOFS ... is this too big a hammer? I don't really like it. There's nothing XFS-specific here - it's the same problem with direct reclaim calling back into the FS and causing massive amounts of problems. If we want to fix this class of problems we just need to do the same thing ext4 and btrfs already do and refuse to call the allocator from reclaim context. Just curious, how much stack does the path up to generic_perform_write use? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>