summaryrefslogtreecommitdiff
path: root/scripts/atomic/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorSam Edwards <cfsworks@gmail.com>2025-12-30 20:05:06 -0800
committerIlya Dryomov <idryomov@gmail.com>2026-01-05 22:46:43 +0100
commit11194b416ef95012c2cfe5f546d71af07b639e93 (patch)
treee5f48d6d342a243e9edddb59d87aac9badfc9ecc /scripts/atomic/git@git.tavy.me:linux.git
parente84b48d31b5008932c0a0902982809fbaa1d3b70 (diff)
libceph: reset sparse-read state in osd_fault()
When a fault occurs, the connection is abandoned, reestablished, and any pending operations are retried. The OSD client tracks the progress of a sparse-read reply using a separate state machine, largely independent of the messenger's state. If a connection is lost mid-payload or the sparse-read state machine returns an error, the sparse-read state is not reset. The OSD client will then interpret the beginning of a new reply as the continuation of the old one. If this makes the sparse-read machinery enter a failure state, it may never recover, producing loops like: libceph: [0] got 0 extents libceph: data len 142248331 != extent len 0 libceph: osd0 (1)...:6801 socket error on read libceph: data len 142248331 != extent len 0 libceph: osd0 (1)...:6801 socket error on read Therefore, reset the sparse-read state in osd_fault(), ensuring retries start from a clean state. Cc: stable@vger.kernel.org Fixes: f628d7999727 ("libceph: add sparse read support to OSD client") Signed-off-by: Sam Edwards <CFSworks@gmail.com> Reviewed-by: Ilya Dryomov <idryomov@gmail.com> Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'scripts/atomic/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions