On Fri, 2 Jul 1999 13:50:31 -0400, tytso@mit.edu said:
> No, this most commonly happens when a user process tries writing to a
> file which is greater than 2GB. The user process doing the write gets
> an error, but ext2_getblk also logs a warning message, which is a bit
> confusing (in this particular case, it probably shouldn't log the
> error).
ext2 now gets this wrong: the 64-bit file code broke the bounds checking
on 32-bit architectures, so we overflowed the 2G mark and ended up
passing negative args into ext2_getblk. No wonder it got upset.
I've a patch I'll be sending you shortly for this, plus a bunch of other
bounds-checking problems in ext2.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/