zstream: consolidate shared code
zstream currently contains three identical copies of dump_record(),
which appear to all be drawn from libzfs_sendrecv.c. The original
is marked internal.
This PR adds zstream_util.[hc] and puts the shared code there along with
a couple of other items in common.
No functional changes.
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Signed-off-by: Garth Snyder <garth at garthsnyder.com>
Closes #18284
[libc][math] Fix FP add/sub for signed-zero operands (#183243)
(-0.0) + (-0.0) and (-0.0) - (+0.0) returned +0.0 instead of -0.0.
Ensure these cases comply with IEEE 754 §6.3 rule.
libclc: Define work_group_barrier
Previously only the old barrier name was implemented. Define this
as an indirection around the new name, and move it to common code.
The target implementations are already provided by __clc_work_group_barrier,
so targets were unnecessarily duplicating these.
This also fixes the default scope, which should be
memory_work_group_scope. Previously this was guessing that
if the flags included global memory, it makes the scope
device which is not the case.
[lldb] Automatic indexing for synthetic children of collections (#174885)
Synthetic providers for collection types use a child name format of
"[N]".
This `ValueObjectSynthetic` to automatically convert child names in this
convention to the index embedded in the subscript string. With this
change, synthetic formatters for collections will only need to implement
`GetIndexOfChildWithName` or `get_child_index` for non-indexed
collection children. Some examples of non-indexed children are
`$$dereference$$` support, or "hidden" children.
The automatic conversion applies to N values that are less than the
number of children reported by the synthetic provider.
NFC: MLIR Indexing Utils comment fix (#183438)
the comment for delinearize was incorrect and swapped modulus and
division, updated comment to match code
[flang-rt] Fix EXECUTE_COMMAND_LINE() on Windows (#184875)
Detect cmd.exe special status code 9009 that indicates "command not
found" condition. Crash the process if "command not found" detected when
CMDSTAT was not specified.
[lldb][Darwin] Don't try to insert breakpoint on corefiles (#184749)
lldb is printing an error that the kext-loaded notification breakpoint
can't be set when debugging a kernel corefile. The breakpoint only needs
to be inserted in live debug sessions.
rdar://170813438
filter out snapshots from iter_mountinfo
This commit adds a non-default parameter to include ZFS
snapshots in iter_mountinfo results. It fixes a bug whereby
automounted snapshots could accidentally leak into mount
info results causing logic relying on this to potentially
walk into snapshot directories. Heuristic is to check
whether source filesystem has an @ character and is ZFS
in order to positively identify snapshots vs other
filesystems. One impact of this heuristic is that users
manually mounting snapshots into normal filesystem paths
will have the snapshot excluded from results. I think
this is probably the correct solution, but one we can
revisit if needed.
(cherry picked from commit 2505bd0f508aad3387a450a5a6c3866ba2d8d909)
filter out snapshots from iter_mountinfo
This commit adds a non-default parameter to include ZFS
snapshots in iter_mountinfo results. It fixes a bug whereby
automounted snapshots could accidentally leak into mount
info results causing logic relying on this to potentially
walk into snapshot directories. Heuristic is to check
whether source filesystem has an @ character and is ZFS
in order to positively identify snapshots vs other
filesystems. One impact of this heuristic is that users
manually mounting snapshots into normal filesystem paths
will have the snapshot excluded from results. I think
this is probably the correct solution, but one we can
revisit if needed.
(cherry picked from commit 2505bd0f508aad3387a450a5a6c3866ba2d8d909)
NAS-140148 / 27.0.0-BETA.1 / filter out snapshots from iter_mountinfo (#18374)
This commit adds a non-default parameter to include ZFS snapshots in
iter_mountinfo results. It fixes a bug whereby automounted snapshots
could accidentally leak into mount info results causing logic relying on
this to potentially walk into snapshot directories. Heuristic is to
check whether source filesystem has an @ character and is ZFS in order
to positively identify snapshots vs other filesystems. One impact of
this heuristic is that users manually mounting snapshots into normal
filesystem paths will have the snapshot excluded from results. I think
this is probably the correct solution, but one we can revisit if needed.
Add --no-preserve-encryption flag
* Add an option to send datasets with params or replicate
without preserving encryption
* Add a test case for the new functionality
Reviewed-by: Paul Dagnelie <paul.dagnelie at klarasystems.com>
Reviewed-by: Brian Behlendorf <behlendorf1 at llnl.gov>
Reviewed-by: Alexander Motin <alexander.motin at TrueNAS.com>
Signed-off-by: Chris Jacobs <idefix2020dev at gmail.com>
Closes #18240
