| commit | f080aec7764da1b378e5ada712d0764ff5a79124 | [log] [tgz] |
|---|---|---|
| author | Sean McBride <sean@rogue-research.com> | Wed Jan 03 19:53:00 2024 -0500 |
| committer | Tormod Volden <debian.tormod@gmail.com> | Fri Jan 19 20:31:47 2024 +0100 |
| tree | d131e9be164644a355353be614ab6f0751a772db | |
| parent | 7719ae5632d0d9bc4d602dc16e25f626cdbfc494 [diff] |
Fix docs about backend functions that lock itransfer->lock In 2013, commit 858b794c added a comment saying "This function gets called with the flying_transfers_lock locked". That appears to have changed with 138b661f. Commit 88778414 improved some stale comments, but missed these. It is clear in the code that the comment is no longer true. The function is *not* called with flying_transfers_lock locked, but it does lock itransfer->lock. References #1410