ls: check fts_children() for errors that may not surface otherwise
In particular, if one simply does a non-recursive `ls` on a directory
that is not accessible, there are some classes of errors that may cause
it to fail that wouldn't be surfaced unless we do an fts_read() that
will recurse into the inaccessible directory. Catch those kinds of
errors here since we cannot expect to an FTS_ERR/FTS_DNR entry to follow
up on them.
PR: 287451
Reviewed by: kib
Discusssed with: des
Differential Revision: https://reviews.freebsd.org/D51056
NAS-139717 / 26.0.0-BETA.1 / Update TrueCommand portal URI. (#18181)
Eliminate usage of 'iX' and 'ixsystems.com' and converting to 'TrueNAS'
and 'truenas.com'
Add logic for preserving existing uid / gid to atomic_rewrite
This commit adds plumbing to accept uid / gid -1 to preserve
existing permissions (if they exist). This is an odd edge-case
but it matches some potential usage of file rewrite in
middleware.
[clang][ssaf] Remove VFS support from SerializationFormat (#180891)
This change removes support for `VFS` in `SerializationFormat`,
introduced in https://github.com/llvm/llvm-project/pull/179516/. `VFS`
only provides a virtual input backend and its matched pair,
`VirtualOutputBackend`, does not provide support for an
`InMemoryOutputBackend`. There was an attempt from our end to implement
this support in https://github.com/llvm/llvm-project/pull/179515 but it
did not succeed. Supporting virtual reads but not virtual writes makes
the SerializationFormat APIs asymmetric. So we have decided to remove
`VFS` support altogether.
---------
Co-authored-by: Balazs Benics <benicsbalazs at gmail.com>
[AArch64][PAC] Emit `!dbg` locations in `*_vfpthunk_` functions
In absence of `!dbg` metadata, it is possible for indirect
authenticated call to be replaced with a direct call instruction
without `!dbg` metadata. This may result in an error reported by
LLVM IR verifier ("inlinable function call in a function with
debug info must have a !dbg location") or an assertion triggered
after inlining this call ("!dbg attachment points at wrong
subprogram for function").
pw: make manual page more friendly for uid/gid search
pw.8 structure is quite different from usual manual page, especially in
describing -o option usage. Specifically, these paragraphs do not
contain "uid/gid" terms, and have "user id"/"group id" instead,
making searching for "override duplicate safety belt" difficult.
Try to simplify such searches.
Also, clarify uid/gid space between 100 and 1000 as "somewhat special",
as it actually is.
Discussed on: russian telegram FreeBSD group
Reviewed by: eugen, novel
MFC after: 1 week
Flush RRD only when TXGs contain data
This change modifies the behavior of spa_sync_time_logger when
flushing the RRD database.
Previously, once the sync interval elapsed, a flush would always
be generated. On solid-state devices, especially when the pool was
otherwise idle, this caused disks to wake up solely to write RRD
data. Since RRD is best-effort telemetry, this behavior is
unnecessary and wasteful.
With this change, spa_sync_time_logger delays flushing until a TXG
that already contains data is being synced. The RRD update is
appended to that TXG instead of forcing the creation of
a new write-only TXG.
During pool export, flushing is forced regardless of whether
the TXG contains user data. At that stage, data durability takes
precedence and a write must be issued.
[5 lines not shown]
[BOLT] Make FoldedIntoFunction always point to root parent (#180855)
After ICF folds functions, FoldedIntoFunction may point to a function
that was also folded. Add a post-processing step at the end of ICF to
flatten all chains so FoldedIntoFunction always points to the ultimate
root parent (a function that is not itself folded).
[lldb][windows] fix undeclared identifier error GetModulePath (#180989)
`LLDB_PYTHON_DLL_RELATIVE_PATH` can be unset while
`LLDB_PYTHON_RUNTIME_LIBRARY_FILENAME` is, since it's set automatically
by CMake. This situation causes a build failure which this patch fixes.
This issue was introduced in
https://github.com/llvm/llvm-project/pull/180784.
[LLDB]Fix asan error from pr/179799 (#180996)
Fix asan error mentioned in [this
comment](https://github.com/llvm/llvm-project/pull/179799#issuecomment-3882710678)
This is breaking our internal builds.
Details: The field needs to be cleaned up or we'll have a leak. We could
also make it a smart pointer if you'd like. But as-is, this is the
quickest way to resolve the issue.
[AMDGPU][GlobalIsel] Add register bank legalization rules for buffer atomic int min max (#180975)
This patch adds register bank legalization rules for buffer atomic int
min max operations in the AMDGPU GlobalISel pipeline.
