-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'zfs send -I' should not require 'hold' permission on src dataset if using 'zfs allow' delegation mechanism #16394
Labels
Type: Defect
Incorrect behavior (e.g. crash, hang)
Comments
whoschek
added a commit
to whoschek/bzfs
that referenced
this issue
Jul 28, 2024
whoschek
added a commit
to whoschek/bzfs
that referenced
this issue
Jul 28, 2024
whoschek
added a commit
to whoschek/bzfs
that referenced
this issue
Jul 28, 2024
whoschek
added a commit
to whoschek/bzfs
that referenced
this issue
Jul 28, 2024
whoschek
added a commit
to whoschek/bzfs
that referenced
this issue
Jul 28, 2024
whoschek
changed the title
'zfs send' on Linux should not require 'hold' permission on src dataset if using 'zfs allow' delegation mechanism
'zfs send -I' on Linux should not require 'hold' permission on src dataset if using 'zfs allow' delegation mechanism
Jul 28, 2024
whoschek
changed the title
'zfs send -I' on Linux should not require 'hold' permission on src dataset if using 'zfs allow' delegation mechanism
'zfs send -I' should not require 'hold' permission on src dataset if using 'zfs allow' delegation mechanism
Aug 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
Describe the problem you're observing
In my testing I discovered that, on Linux and FreeBSD, the 'send' permission is sufficient for 'zfs send -i' to succeed if the 'zfs allow' delegation mechanism is used to grant permissions to a non-root user (which is expected), whereas for 'zfs send -I' (note the uppercase I) an additional 'hold' permission is required as well (which isn't expected). Otherwise the following error happens on
zfs send -I wb_src/tmp@u1 wb_src/tmp@u3
cannot hold: permission denied
The hold permission should not be required. Presumably, the implementation of 'zfs send' intermittently uses a hold but that should better not bubble up to the level of affecting user level permission requirements.
Interestingly, a version with -i (skip intermediate snapshots) instead of -I (include intermediate snapshots) does not fail:
zfs send -i wb_src/tmp@u1 wb_src/tmp@u3 # does not fail
Describe how to reproduce the problem
Here is a reliable minimal reproducer:
The exact versions of zfs/FreeBSD/Linux that were tested are listed above.
Include any warning/errors/backtraces from the system logs
The text was updated successfully, but these errors were encountered: