ping: fix listing test cases when scapy is not installed
The ATF-python test program was attempting to list test cases that
require scapy. But it attempted to import the scapy module before the
test cases had been listed, resulting in an ImportError that kyua
interpreted as a test program crash.
Fix this behavior by handling that ImportError well enough to list test
cases, but not run them. If scapy isn't present, Kyua will refuse to
run the test cases. But it needs to be able to list them in order to
know to skip them.
Sponsored by: ConnectWise
Reviewed by: maxim
Differential Revision: https://reviews.freebsd.org/D56765
(cherry picked from commit 3e845b1090565912375c5578cf0399d27b7fa70c)
[MLIR][CMake] Downgrade ocloc not found diagnostic from WARNING to STATUS (#198296)
When ocloc is not found, the CMake configuration emits a WARNING which
can be noisy for users who have no interest in Intel XeVM native binary
compilation (e.g., those targeting only AMDGPU or NVPTX). Downgrade the
diagnostic to STATUS since this is an expected configuration when ocloc
is not installed.
For example:
```bash
CMake Warning at /llvm-project/mlir/lib/Target/LLVM/CMakeLists.txt:246 (message):
ocloc not found, MLIRXeVMTarget will not be able to use ocloc for native
binary compilation.
```
PR bin/60275 discard some arriving signals
The PR is only peripherally relevant to this, but it is all much
the same problem, over a fork() trapped signals are maintained,
and sh does not really want that.
In this case, when there is a vfork() a signal arriving for a
child (whether or not it should arrive and be processed) can be
treated as if it arrived for the parent, and cause a trap action
to be executed by the parent. (Never observed to have happened,
as best I am aware, but certainly looks as if it could.)
Avoid that, by making sure that the child process never records
a signal as having occurred, when it is being a vfork child
(while the parent is sharing memory with it).
Doing this meant making one variable that was previously local
to eval.c globally visible (exposing it in eval.h), and then
because the same name is used as a parameter in many other
[17 lines not shown]
[libc++] Refactor `std::midpoint` tests and add constraint checks (#175388)
Refactor the `std::midpoint` tests and replace the verify test with
constraint checks.
[Offload] Fix llvm-gpu-loader after new argument (#198681)
Summary:
New argument added but was not included here. This gets out of sync just
because there's no reasonable way to build offload and this tool, it's
an unsolvable phase ordering problem so we just dlopen it.
nfs_clsubs.c: Fix ncl_getcookie() when "pos" is negative
In ncl_getcookie(), a very large value for "off" for
a directory can result in "pos" being set to a bogus
value (including a negative one), due to truncation.
When "pos" is negative, is can skip past the
while (pos >= NFSNUMCOOKIES) loop and return a
bogus pointer instead of NULL.
This patch changes the type to u_int and also adds
a sanity check for a very large "off" to ensure that
a NULL pointer is returned for this case.
This bug has been in the code for decades and I am
not aware of any report of it causing a problem for
users.
(cherry picked from commit 448b4c3f7f7dd4c7e1707d7b833a26294c297182)
Fix use-after-free in IOTransport::OnRead on client disconnect (#198548)
When an MCP client disconnects (EOF), `IOTransport::OnRead` called
`handler.OnClosed()` before resetting `m_read_handle`. The MCP server's
`OnClosed` handler erases the client from `m_instances`, destroying both
the transport (`this`) and the binder (`handler`). The subsequent
`m_read_handle.reset()` then accessed the destroyed transport's member,
causing a use-after-free (SIGSEGV).
* thread #1, stop reason = signal SIGSEGV: address not mapped to object
(fault address=0x28)
* frame #0: 0x00007ff5d4d5afda
liblldb.so.23.2`lldb_private::transport::IOTransport<lldb_protocol::mcp::ProtocolDescriptor>::OnRead(lldb_private::MainLoopBase&,
lldb_private::transport::JSONTransport<lldb_protocol::mcp::ProtocolDescriptor>::MessageHandler&)
+ 1274
frame #1: 0x00007ff5d1140ad8
liblldb.so.23.0`lldb_private::MainLoopPosix::Run() + 408
frame #2: 0x00007ff5d1760c1c
liblldb.so.23.0`std::thread::_State_impl<std::thre
[14 lines not shown]
[alpha.webkit.UncountedCallArgsChecker] Check arguments of CXXConstructExpr (#198454)
Check arguments of CXXConstructExpr like CallExpr.
This PR fixes a subtle bug in isCtorOfRetainPtrOrOSPtr that it was missing a check for OSObjectPtr, and it was getting an empty string for the name when getting called on a CXXConstructorDecl as well as similar bugs in isCtorOf* functions.
nfs_clsubs.c: Fix ncl_getcookie() when "pos" is negative
In ncl_getcookie(), a very large value for "off" for
a directory can result in "pos" being set to a bogus
value (including a negative one), due to truncation.
When "pos" is negative, is can skip past the
while (pos >= NFSNUMCOOKIES) loop and return a
bogus pointer instead of NULL.
This patch changes the type to u_int and also adds
a sanity check for a very large "off" to ensure that
a NULL pointer is returned for this case.
This bug has been in the code for decades and I am
not aware of any report of it causing a problem for
users.
(cherry picked from commit 448b4c3f7f7dd4c7e1707d7b833a26294c297182)
[clang][driver][darwin] Hold onto full triples in Darwin SDKPlatformInfo (#197791)
The architecture can be relevant when determining if an SDK supports a
particular triple. Record the full triples in SDKPlatformInfo instead of
all of the non-architecture triple components.
Assisted-by: Claude Code
rdar://172876443
[flang] Improved FIR AA for acc.compute_region. (#198635)
We should actually treat the operand<->block-arg association
in `acc.compute_region` as a pass-through link, so that we can
accumulate the whole chain of addressing inside the compute region.
This is especially important for acc routines, where all `[hl]fir.declare`
operations are located inside `acc.compute_region`. The input operand,
in this case, is not a result of ACC entry/init operation.
The change in `FIROps.cpp` should be NFC, currently. I made it
just to align the pass-through handling with the AA change.
Even though I effectively replaced `ACC_DATA_ENTRY_OPS` with
`ACC_DATA_ENTRY_AND_INIT_OPS`, this change is not testable, because
boxed reductions are currently unsupported.
cap_net: do not allow new limits to drop keys from the old ones
If the old limit had family/hosts/sockaddr set, the new limit must
have them too. Before, a missing key in the new limit was treated as
"allow any", which let a caller silently extend their limits.
Reported by: Joshua Rogers of AISLE Research Team
Reviewed by: markj
MFC after: 1 day
Differential Revision: https://reviews.freebsd.org/D56991
(cherry picked from commit d705a519525f2acae3c1efba11436ec6ee8aea0a)
cap_net: do not allow new limits to drop keys from the old ones
If the old limit had family/hosts/sockaddr set, the new limit must
have them too. Before, a missing key in the new limit was treated as
"allow any", which let a caller silently extend their limits.
Reported by: Joshua Rogers of AISLE Research Team
Reviewed by: markj
MFC after: 1 day
Differential Revision: https://reviews.freebsd.org/D56991
(cherry picked from commit d705a519525f2acae3c1efba11436ec6ee8aea0a)
net-mgmt/thanos: Fix BUILD_DATE syntax to fix build
* Change the syntax of BUILD_DATE after switching to GO_LDFLAGS as
port was using double quotes but Uses/go.mk has single quotes where it
interpolates GO_LDFLAGS, which requires use of different syntax.
* Also switch date format of BUILD_DATE to classic ISO 8601.
PR: 295384
Reported by: Chad Jacob Milios <milios at ccsys.com>
Approved by: db@, yuri@ (Mentors, implicit)
Fixes: 2af7cdf6fd59 * net-mgmt/thanos: improve port
