ddb(4), crash(8): Make `show all locks' work without LOCKDEBUG.
Any lwp currently waiting for a _contended_ lock will now record a
pointer to that lock in struct lwp::l_ld_wanted, even without
LOCKDEBUG. We can't tell who holds shared locks or spin locks, but we
can at least tell what lock a thread is waiting for when it's spinning
for a spin lock, and generally present the graph of current lock
dependencies reasonably well this way.
PR kern/60030: ddb/crash: show all locks without LOCKDEBUG
kernel: Track what lock each lwp is waiting for without LOCKDEBUG.
This is reasonably cheap -- one extra pointer on the stack, couple
extra stores when _waiting_ (spinning or sleeping) for a _contended_
lock -- and doesn't change the kernel ABI. Will enable us to get
diagnostics from crash dumps when, e.g., there's a softint deadlock
tripping a heartbeat panic.
PR kern/60030: ddb/crash: show all locks without LOCKDEBUG
"if PWD references the current directory, then PWD is assumed to be the
name of the current directory" is tautologically confusing.
Just state that for '-L' $PWD is _printed_ (under the right circumstances).
vchiq: Back port of the change
commit 49bec49fd7f273ec114e2e533c1bb8f21a654aaf
Author: Michael Zoran <mzoran at crowfest.net>
Date: Sun Oct 30 05:55:07 2016 -0700
staging: vc04_services: remove vchiq_copy_from_user
The vchiq_copy_from_user function is not portable
and is consider "bad practice." Replace this function
with a callback based mechanism that is passed downward
on the stack. When it is actually time to copy the data,
the callback is called to copy the data into the message.
This callback is provided internally for userland calls
through ioctls on the device.
NOTE: Internal clients will need to be modified to work
with the new internal API.
[26 lines not shown]
vchiq: Apply change from upstream
commit 6e474d8e3981a63b6e1cf11b838014ed52499804
Author: Stefan Wahren <wahrenst at gmx.net>
Date: Wed Oct 26 18:34:19 2016 +0000
staging: vchiq_shim: avoid code duplication
Rearrange the polling loops in order to avoid code duplication. Btw we fix
the style of the comments.
Signed-off-by: Stefan Wahren <stefan.wahren at i2se.com>
Reviewed-by: Eric Anholt <eric at anholt.net>
Signed-off-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org>
www/ruby-aws-partitions: update to 1.1281.0
1.1281.0 (2026-08-14)
* Feature - Updated the partitions source data that determines the AWS
service regions and endpoints.
net/ruby-net-ping: update to 2.1.1
pkgsrc change: remove a pkglint warning, wrong CATEGORIES.
2.1.0 (2026-08-08)
* Publish platform-specific gem metadata so Linux installs cap2 and current
Windows RubyInstaller installs win32-security for ICMP support #44.
* Fix the FreeBSD ping6 timeout option #43.
* Add Ruby 4.0 to the test matrix and add win32ole as an explicit Windows
dependency, since it is no longer a default gem as of Ruby 4.0 #41.
* Move Net::Ping::VERSION into its own file so the gemspec version can no
longer drift out of sync with it #37.
* Fix Net::Ping::External#ping6 setting a spurious "undefined method '=~'
[8 lines not shown]
devel/ruby-simplecov: update to 1.1.1
pkgsrc change: remove pkglint warnings from DESCR.
1.1.1 (2026-08-12)
What's Changed
* Bump step-security/harden-runner from 2.20.0 to 2.20.1 by
@dependabot[bot] in #1258
* rspec-conductor Support by @sferik in #1259
Contributors
* @sferik
* @dependabot
devel/ruby-io-event: update to 1.19.5
1.19.5 (2026-08-14)
* Preserve the original exception or non-local control flow when
IO::Event::WorkerPool cancellation interrupts a blocked fiber, while still
cancelling and draining the in-flight blocking operation before returning
control to Ruby.
p5-Net-OAuth: update to 0.32.
0.32 Sun 16 Aug 00:51:04 BST 2026
[Security]
- The Net::OAuth smart_require function no longer memoizes
failures, which allowed attackers to exhaust memory with
requests for invalid signature methods. CVE-2026-72888
- Net::OAuth::Client no longer allows silent downgrades from
OAuth 1.0a to 1.0 when the remote provider drops the
oauth_verifier. The behavior can be re-enabled with the
allow_v1a_downgrade option. CVE-2026-72887
[Bug Fixes]
- RSA-SHA1 now pins PKCS#1 v1.5 padding and the SHA-1 hash rather
than inheriting Crypt::OpenSSL::RSA's defaults, which have drifted
(SHA-256 in 0.29_01, RSA-PSS in 0.35). Against 0.35 and later this
produced RSA-PSS signatures that no RFC 5849 3.4.3 compliant server
will accept. Reported as Debian #1142954.
[98 lines not shown]
