summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
a4bfba8)
Do not clear the AFS_NEXT flag in afs_send_chunk() and increase mmd->events.
Fixes a (rare) problem where the next command did not work.
if (tv_diff(&due, &now, NULL) > 0)
return;
buf = af->read_chunk(mmd->current_chunk, &ret);
if (tv_diff(&due, &now, NULL) > 0)
return;
buf = af->read_chunk(mmd->current_chunk, &ret);
- mmd->new_afs_status_flags &= ~(AFS_NEXT | AFS_REPOS);
+ mmd->new_afs_status_flags &= ~AFS_REPOS;
if (!buf) {
if (ret < 0)
mmd->new_afs_status_flags = AFS_NEXT;
if (!buf) {
if (ret < 0)
mmd->new_afs_status_flags = AFS_NEXT;
if (argc)
return -E_COMMAND_SYNTAX;
mmd_lock();
if (argc)
return -E_COMMAND_SYNTAX;
mmd_lock();
mmd->new_afs_status_flags |= AFS_NEXT;
mmd_unlock();
return 1;
mmd->new_afs_status_flags |= AFS_NEXT;
mmd_unlock();
return 1;