diff options
author | Evgeniy Dushistov <dushistov@mail.ru> | 2006-08-27 01:23:46 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-08-27 11:01:31 -0700 |
commit | ecdc63948763586e101108dfe1ba316ec069fe39 (patch) | |
tree | a127e8fef9ce30007a357cff51f092ab500f8e7f /kernel | |
parent | c37336b078ba9d2ff38c535b194996a7ad6e69f8 (diff) | |
download | linux-ecdc63948763586e101108dfe1ba316ec069fe39.tar.gz linux-ecdc63948763586e101108dfe1ba316ec069fe39.tar.bz2 linux-ecdc63948763586e101108dfe1ba316ec069fe39.zip |
[PATCH] ufs: truncate correction
1) When we allocated last fragment in ufs_truncate, we read page, check
if block mapped to address, and if not trying to allocate it. This is
wrong behaviour, fragment may be NOT allocated, but mapped, this
happened because of "block map" function not checked allocated fragment
or not, it just take address of the first fragment in the block, add
offset of fragment and return result, this is correct behaviour in
almost all situation except call from ufs_truncate.
2) Almost all implementation of UFS, which I can investigate have such
"defect": if you have full disk, and try truncate file, for example 3GB
to 2MB, and have hole in this region, truncate return -ENOSPC. I tried
evade from this problem, but "block allocation" algorithm is tied to
right value of i_lastfrag, and fix of this corner case may slow down of
ordinaries scenarios, so this patch makes behavior of "truncate"
operations similar to what other UFS implementations do.
Signed-off-by: Evgeniy Dushistov <dushistov@mail.ru>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions