summaryrefslogtreecommitdiff
path: root/fs/squashfs/xattr.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2016-04-10 16:52:24 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2016-04-10 16:52:24 -0700
commit9f2394c9be47a754bae9e4b6d382bdd4d77d0a11 (patch)
tree6ace4923e1038f45aa57acb5f1c1166cad61c5c3 /fs/squashfs/xattr.c
parent5b5b7fd185e997ebc18f76b98b9f4ff148d3f5bb (diff)
Revert "ext4: allow readdir()'s of large empty directories to be interrupted"
This reverts commit 1028b55bafb7611dda1d8fed2aeca16a436b7dff. It's broken: it makes ext4 return an error at an invalid point, causing the readdir wrappers to write the the position of the last successful directory entry into the position field, which means that the next readdir will now return that last successful entry _again_. You can only return fatal errors (that terminate the readdir directory walk) from within the filesystem readdir functions, the "normal" errors (that happen when the readdir buffer fills up, for example) happen in the iterorator where we know the position of the actual failing entry. I do have a very different patch that does the "signal_pending()" handling inside the iterator function where it is allowable, but while that one passes all the sanity checks, I screwed up something like four times while emailing it out, so I'm not going to commit it today. So my track record is not good enough, and the stars will have to align better before that one gets committed. And it would be good to get some review too, of course, since celestial alignments are always an iffy debugging model. IOW, let's just revert the commit that caused the problem for now. Reported-by: Greg Thelen <gthelen@google.com> Cc: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/squashfs/xattr.c')
0 files changed, 0 insertions, 0 deletions