Searched hist:"35 edec1d52c075975991471d624b33b9336226f2" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/ocfs2/ |
| H A D | alloc.h | diff 35edec1d52c075975991471d624b33b9336226f2 Fri Jul 06 16:41:18 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: update truncate handling of partial clusters
The partial cluster zeroing code used during truncate usually assumes that
the rightmost byte in the range to be zeroed lies on a cluster boundary.
This makes sense for truncate, but punching holes might require zeroing on
non-aligned rightmost boundaries.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
| H A D | alloc.c | diff 35edec1d52c075975991471d624b33b9336226f2 Fri Jul 06 16:41:18 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: update truncate handling of partial clusters
The partial cluster zeroing code used during truncate usually assumes that
the rightmost byte in the range to be zeroed lies on a cluster boundary.
This makes sense for truncate, but punching holes might require zeroing on
non-aligned rightmost boundaries.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|
| H A D | file.c | diff 35edec1d52c075975991471d624b33b9336226f2 Fri Jul 06 16:41:18 CDT 2007 Mark Fasheh <mark.fasheh@oracle.com> ocfs2: update truncate handling of partial clusters
The partial cluster zeroing code used during truncate usually assumes that
the rightmost byte in the range to be zeroed lies on a cluster boundary.
This makes sense for truncate, but punching holes might require zeroing on
non-aligned rightmost boundaries.
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
|