Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D darshan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • darshan
  • darshan
  • Issues
  • #314

Closed
Open
Created Apr 09, 2021 by Philip Carns@carnsOwner

offset tracking in posix and stdio module are not thread safe in some situations

This is especially true if threads hold distinct file pointers or file descriptors open to the same file concurrently. In this case Darshan will map them to the same underlying file record and use a shared offset variable to track previous position.

In the POSIX case this would affect DXT tracing, because that shared offset field is used to generate the file offset in the trace.

In the STDIO case the same problem exists, plus the shared offset is also used to calculate access sizes for conventional STDIO counters too, since not all STDIO functions report the number of bytes moved.

Problem identified by @glock .

Assignee
Assign to
Time tracking