Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
codes
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • codes
  • codes
  • Issues
  • #21

Closed
Open
Opened Jan 14, 2016 by Jonathan Jenkins@jenkins
  • Report abuse
  • New issue
Report abuse New issue

ROSS cancel event ordering patch

Reproduce in the codes-net repo as follows:

make tests
cd tests
mpiexec -n 2 ./concurrent-msg-recv --sync=3 --codes-config=conf/concurrent_msg_recv.conf

ROSS patch to address the problem is attached. The fix is to prevent the network code from bypassing scheduling in the fast case if the cancel queue isn't empty. Otherwise re-issued forward events may bypass cancellation events, causing the model to see two identical forward events without a rollback in between them. This can cause problems for models of stateful protocols.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
defect ROSS
Assign labels
  • View project labels
Reference: codes/codes#21