All posts by corbet

[$] QUIC for the kernel

Post Syndicated from corbet original https://lwn.net/Articles/1029851/

The QUIC transport-layer network protocol is not exactly new; it was first
covered here in 2013. Despite carrying a
significant part of the traffic on the Internet, QUIC has been anything but
quick when it comes to getting support into the Linux kernel. The pace
might be picking up, though; Xin Long has posted the first set of
patches
intended to provide mainline support for this protocol.

Security updates for Tuesday

Post Syndicated from corbet original https://lwn.net/Articles/1030930/

Security updates have been issued by AlmaLinux (tomcat9), Debian (djvulibre, libcommons-fileupload-java, libowasp-esapi-java, and tomcat9), Fedora (cef, dpkg, mingw-gdk-pixbuf, and mingw-python3), Gentoo (Roundcube), Oracle (avahi, cloud-init, fence-agents, git, kernel, and valkey), Red Hat (wireshark), SUSE (afterburn, apache2, busybox, java-21-openjdk, kernel, kernel-livepatch-MICRO-6-0-RT_Update_10, lemon, libexslt0, libgcrypt, libxml2-2, php8, postgresql17, python, python-oslo.utils, python311, python312, python313, and sudo), and Ubuntu (drupal7, erlang, fdkaac, gobgp, jq, linux-aws, linux-aws-6.8, linux-gke, linux-gkeop, linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency, linux-oracle, linux-oracle-6.8, linux-kvm, linux-oracle, and ruby-nokogiri).

Malicious packages uploaded to the Arch Linux AUR

Post Syndicated from corbet original https://lwn.net/Articles/1030603/

The Arch Linux project has sent out an
advisory
warning that a set of malicious packages, containing a remote
access trojan, were uploaded to the Arch User Repository (AUR). The
affected packages were librewolf-fix-bin, firefox-patch-bin, and
zen-browser-patched-bin. “We strongly encourage users that may have
installed one of these packages to remove them from their system and to
take the necessary measures in order to ensure they were not
compromised.
“

The end of Clear Linux

Post Syndicated from corbet original https://lwn.net/Articles/1030563/

Intel has announced the
abrupt end of its Clear Linux cloud-oriented distribution:

After years of innovation and community collaboration, we’re ending
support for Clear Linux OS. Effective immediately, Intel will no
longer provide security patches, updates, or maintenance for Clear
Linux OS, and the Clear Linux OS GitHub repository will be archived
in read-only mode. So, if you’re currently using Clear Linux OS, we
strongly recommend planning your migration to another actively
maintained Linux distribution as soon as possible to ensure ongoing
security and stability.

[$] Scheduler medley: time-slice extension, sched_ext deadline servers, and LRU batching.

Post Syndicated from corbet original https://lwn.net/Articles/1029093/

Decades after its creation, the Linux CPU scheduler remains an area
of active development; it is difficult to find a time slice to cover every
interesting scheduler change. In an attempt to catch up, the time has come
to round-robin through a few patches that have been circulating recently.
The work at hand focuses on a new attempt at time-slice extension, the
creation of a deadline server for sched_ext tasks, and keeping tasks on
isolated CPUs from being surprised by LRU batching.

Security updates for Wednesday

Post Syndicated from corbet original https://lwn.net/Articles/1030106/

Security updates have been issued by Oracle (cloud-init, emacs, firefox, glib2, go-toolset:rhel8, kernel, lz4, python-setuptools, python3.11-setuptools, python3.12-setuptools, and socat), Red Hat (fence-agents, glib2, glibc, java-17-openjdk, kernel, kernel-rt, python-setuptools, python3.11-setuptools, and python3.12-setuptools), Slackware (libxml2), SUSE (glib2, gpg2, kernel, libxml2, poppler, rmt-server, runc, stalld, and xen), and Ubuntu (jpeg-xl).

[$] Enforcement (or not) for module-specific exported symbols

Post Syndicated from corbet original https://lwn.net/Articles/1029492/

Loadable kernel modules require access to kernel data structures and
functions to get their job done; the kernel provides this access by way of
exported symbols. Almost since this mechanism was created, there have been
debates over which symbols should be exported, and how. The 6.16 kernel
gained a new export mechanism that limits access to symbols to specific
kernel modules. That code is likely to change soon, but the addition
of an enforcement mechanism has since been backed out.

Security updates for Tuesday

Post Syndicated from corbet original https://lwn.net/Articles/1029919/

Security updates have been issued by Debian (ffmpeg), Fedora (gnutls, linux-firmware, mingw-djvulibre, mingw-python-requests, and salt), Mageia (qtimageformats6), Oracle (gnome-remote-desktop, golang, kernel, libxml2, and perl-File-Find-Rule), SUSE (gstreamer-plugins-base, gstreamer-plugins-good, kernel, and protobuf), and Ubuntu (apport, glibc, gnutls28, and roundcube).

Parrot 6.4 released

Post Syndicated from corbet original https://lwn.net/Articles/1029857/

Parrot is a Debian-based
distribution with an emphasis on security improvement and tools; the 6.4
release
is now available. “Many tools, like Metasploit, Sliver,
Caido and Empire received important updates, the Linux kernel was updated
to a more recent version, and the latest LTS version of Firefox was
provided with all our privacy oriented patches.
“.

Kernel prepatch 6.16-rc6

Post Syndicated from corbet original https://lwn.net/Articles/1029716/

Linus has released 6.16-rc6 for testing;
it includes a fix for a somewhat scary regression that came up over the
week.

So I was flailing around blaming everybody and their pet hamster,
because for a while it looked like a drm issue and then a netlink
problem (it superficially coincided with separate issues with both
of those subsystems).

But I did eventually figure out how to trigger it reliably and then
it bisected nicely, and a couple of days have passed, and I’m
feeling much better about the release again. We’re back on track,
and despite that little scare, I think we’re in good shape.

[$] SFrame-based stack unwinding for the kernel

Post Syndicated from corbet original https://lwn.net/Articles/1029189/

The kernel’s perf
events subsystem
can produce high-quality profiles, with full
function-call chains, of resource usage
within the kernel itself. Developers, however, often would like to see
profiles of the whole system in one integrated report with, for example,
call-stack information that crosses the boundary between the kernel and
user space. Support for unwinding user-space call stacks in the perf
events subsystem is currently inefficient at best. A long-running effort
to provide reliable, user-space call-stack unwinding within the kernel,
which will improve that situation considerably, appears to be reaching
fruition.