diff options
author | Raghavendra G <raghavendra@gluster.com> | 2010-02-23 00:04:55 +0000 |
---|---|---|
committer | Anand V. Avati <avati@dev.gluster.com> | 2010-02-22 23:27:06 -0800 |
commit | d9d6edc1252dcacbd4c7e2032be36279d3307799 (patch) | |
tree | 5d777e6f15194230c0a62ca2218d8e4f4c1a3d63 /glusterfs.spec.in | |
parent | af004cdf11918901ac6a79d32cdef3f6cc67525b (diff) |
performance/write-behind: fix data corruption while aggregating the adjacent contiguous iobufs into a single iobuf
- while aggregating, we should make sure that the destination has enough
memory. __wb_collapse_write_bufs assumed that destination vector's iov_base
was aligned to the start of an iobuf and hence memory of page_size is
available for aggregation. This assumption is not always true, like in the
configuration consisting afr->write->io-cache (afr is on top). Refer to the
bug url for more details.
Signed-off-by: Raghavendra G <raghavendra@gluster.com>
Signed-off-by: Anand V. Avati <avati@dev.gluster.com>
BUG: 542 (write-behind crashes)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=542
Diffstat (limited to 'glusterfs.spec.in')
0 files changed, 0 insertions, 0 deletions