diff options
author | Matthew Ahrens <[email protected]> | 2020-04-20 10:12:48 -0700 |
---|---|---|
committer | GitHub <[email protected]> | 2020-04-20 10:12:48 -0700 |
commit | 1f043c8be1bf575bae1088f150cf17b35184ad12 (patch) | |
tree | 8d34f8ded3fff070305ef1fe06df98f915717f2c /.gitignore | |
parent | c614fd6e12c0fe2636a82b341e9ab9d150ee3c8a (diff) |
Fix zfs send progress reporting
The progress of a send is supposed to be reported by `zfs send -v`, but
it is not. This works by creating a new user thread (with
pthread_create()) which does ZFS_IOC_SEND_PROGRESS ioctls to check how
much progress has been made. This IOCTL finds the specified send (since
there may be multiple concurrent sends in the system). The IOCTL also
checks that the specified send was started by the current process.
On Linux, different threads of the same process are represented as
different `struct task_struct`s (and, confusingly, have different
PID's). To check if if two threads are in the same process, we need to
check if they have the same `struct task_struct:group_leader`.
We used to to this correctly, but it was inadvertently changed by
30af21b02569 (Redacted Send) to simply check if the current
`struct task_struct` is the one that started the send.
This commit changes the code back to checking if the send was started by
a `struct task_struct` with the same `group_leader` as the calling
thread.
Reviewed-by: Ryan Moeller <[email protected]>
Reviewed-by: Chris Wedgwood <[email protected]>
Reviewed-by: Paul Dagnelie <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Matthew Ahrens <[email protected]>
Closes #10215
Closes #10216
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions