Open grahamc opened 3 years ago
When a solution is found for this bug, we should be sure not to let the work done in https://github.com/openzfs/zfs/pull/12335 be lost, and include those tests.
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.
I don't think this is resolved. @grahamc this should remain open, right?
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.
I don't think this is solved, and I wish it were, though I'm no longer pursuing this.
On Sun, Oct 15, 2023, at 11:37 AM, stale[bot] wrote:
This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/openzfs/zfs/issues/12337#issuecomment-1763426662, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASXLEHOHDMLGUMRT5EQ6TX7P7KBAVCNFSM5AA4DD32U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZWGM2DENRWGYZA. You are receiving this because you were mentioned.Message ID: @.***>
System information
and by @nshalman:
Describe the problem you're observing
A ZFS Channel Program can't access, seemingly, just these two properties:
enc.lua:
results in:
and for @nshalman:
Describe how to reproduce the problem
Create an encrypted dataset:
then edit
enc.lua
from above to point to the dataset and execute it, note theencryption
andencryptionroot
fields are not correctly reported.Include any warning/errors/backtraces from the system logs
none
I've opened PR #12335 adding a test to verify channel programs can access these two fields. As expected, the test fails in the sanity tests: