diff options
author | Alex Elder <elder@inktank.com> | 2012-06-11 14:57:13 -0500 |
---|---|---|
committer | Sage Weil <sage@inktank.com> | 2012-07-05 21:14:18 -0700 |
commit | abdaa6a849af1d63153682c11f5bbb22dacb1f6b (patch) | |
tree | 449810fd8346abb8ba9b608aaa0f2d8a250696d2 /arch | |
parent | 572c588edadaa3da3992bd8a0fed830bbcc861f8 (diff) | |
download | op-kernel-dev-abdaa6a849af1d63153682c11f5bbb22dacb1f6b.zip op-kernel-dev-abdaa6a849af1d63153682c11f5bbb22dacb1f6b.tar.gz |
libceph: don't use bio_iter as a flag
Recently a bug was fixed in which the bio_iter field in a ceph
message was not being properly re-initialized when a message got
re-transmitted:
commit 43643528cce60ca184fe8197efa8e8da7c89a037
Author: Yan, Zheng <zheng.z.yan@intel.com>
rbd: Clear ceph_msg->bio_iter for retransmitted message
We are now only initializing the bio_iter field when we are about to
start to write message data (in prepare_write_message_data()),
rather than every time we are attempting to write any portion of the
message data (in write_partial_msg_pages()). This means we no
longer need to use the msg->bio_iter field as a flag.
So just don't do that any more. Trust prepare_write_message_data()
to ensure msg->bio_iter is properly initialized, every time we are
about to begin writing (or re-writing) a message's bio data.
Signed-off-by: Alex Elder <elder@inktank.com>
Reviewed-by: Sage Weil <sage@inktank.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions