Language Selection

English French German Italian Portuguese Spanish

Linux 5.5

Filed under
Linux

So this last week was pretty quiet, and while we had a late network
update with some (mainly iwl wireless) network driver and netfilter
module loading fixes, David didn't think that warranted another -rc.
And outside of that, it's really been very quiet indeed - there's a
panfrost driver update too, but again it didn't really seem to make
sense to delay the final release by another week.

Outside of those, it's all really tiny, even if some of those tiny
changes touched some core files.

So despite the slight worry that the holidays might have affected the
schedule, 5.5 ended up with the regular rc cadence and is out now.

That means that the merge window for 5.6 will open tomorrow, and I
already have a couple of pull requests pending. The timing for this
next merge window isn't optimal for me - I have some travel and other
things going on during the same two weeks, but hopefully it won't be
all that noticeable.  But there might be random timezones, odd hours,
and random delays because of that. I try to avoid scheduling things
during the merge window, but hey, it doesn't always work out, and I'd
have to delay things by two weeks to avoid the conflicts, which just
doesn't seem worth it.

Particularly since it's not necessarily going to be a problem to begin
with. We'll see.

Anyway. Go out and test 5.5, and start sending me those pull requests
for all the new development that is ready,

                    Linus

Read more

Also: Linux 5.5 Released With Many Hardware Support Improvements

Linux Kernel 5.5 Officially Released, This Is What’s New

Linux 5.5 Release – Main Changes, Arm, MIPS and RISC-V Arch

Linus Torvalds Releases Linux Kernel 5.5 With Better Hardware

  • Linus Torvalds Releases Linux Kernel 5.5 With Better Hardware Support

    With the regular milestone of Release Candidate (rc7), Linus Torvalds has announced the first stable release of the Linux kernel 5.5 for the general public.

    Apart from the last-minute network driver fixes, Linux 5.5 includes various improvements for security, the new and upcoming hardware platforms such as Raspberry Pi 4, Intel processors, and Chromebooks.

The 5.5 kernel is out

  • The 5.5 kernel is out

    In the end, Linus decided to release the 5.5 kernel rather than going for another prepatch. "So despite the slight worry that the holidays might have affected the schedule, 5.5 ended up with the regular rc cadence and is out now."

10 Best Features in Linux 5.5, Out Now

  • 10 Best Features in Linux 5.5, Out Now

    Serving as the latest stable version of the Linux kernel, the Linux 5.5 release was announced on the Linux Kernel Mailing List (LKML) by Linus Torvalds, who said: “Despite the slight worry that the holidays might have affected the schedule, 5.5 ended up with the regular [release candidate] cadence and is out now.”

    He goes on to describe the release as being “really tiny” — make of that what you will — and has named it “Kleptomaniac Octopus”.

    Linux 5.5 is likely to be included in the upcoming Ubuntu 20.04 LTS release, which is due for release in mid April. This kernel version will also be back-ported to Ubuntu 18.04 LTS later in the year as part of the Ubuntu HWE stack.

    If you want to install the mainline kernel on Ubuntu or another Linux distribution right now you can — but doing so is not recommended, comes with no support, and may break your system (but don’t worry: you get to keep both halves if it does).

Linus Torvalds Releases Linux Kernel 5.5 With Better Feature

Linux 5.5 now in Sparky Linux and in Slashdot

  • Linux kernel 5.5 [in Sparky Linux]

    The first release of the Linux kernel of the new 5.5 line landed in Sparky “unstable” repository.

    [...]

    Then reboot your machine to take effects.

    To quick remove older version of a Linux kernel, simply run APTus-> System-> Uninstall Old Kernel tool.

  • Linux 5.5 Released

    Linus Torvalds has announced Linux 5.5 release, codenamed as Kleptomaniac Octopus.The latest version of the open source operating system kernel brings RAID1 with 3- and 4- copies to btrfs filesystem, ext4 gets direct I/O via iomap together with fscrypt supporting smaller block sizes, and you can now use SMB as root filesystem. AMD OverDrive overclocking is now supported on Navi GPUS, wake-on-voice on newer Google Chromebooks is now supported. Added was a Logitech keyboard driver. KUnit is a new unit testing framework for the kernel. There are many more new features which you can read about on Kernel Newbies changelog page. For downloads visit The Linux Kernel Archives.

Linux 5.5 “Kleptomaniac Octopus” Officially Launched

  • Linux 5.5 “Kleptomaniac Octopus” Officially Launched

    Codenamed Kleptomaniac Octopus, the new Linux release comes with a series of major improvements, including full Raspberry Pi 4 and Chromebook Wake-On-Voice support.

    “Despite the slight worry that the holidays might have affected the schedule, 5.5 ended up with the regular rc cadence and is out now,” Linus Torvalds announced.

Linux 5.5 officially released

  • Linux 5.5 officially released with a couple of hardware improvements

    A couple of days ago, Linus Torvalds announced that the Linux 5.5 stable version is coming soon. Now, there are reports that the stable version of Linux 5.5 is available. Torvalds pointed out in the release announcement that despite the increase in patches this week and concerns about the possible extension of the Linux 5.5 cycle due to downtime around Christmas and New Year holidays, it chose to release the 5.5 kernel on time.

“Welcome, Kleptomaniac Octopus” – Linux 5.5 Lands

  • “Welcome, Kleptomaniac Octopus” – Linux 5.5 Lands, with Improved Hardware Support

    Linux Torvalds has released the first stable Linux kernel update of 2020, Linux 5.5 – and it’s on schedule despite the worries that downtime over the holidays would have an impact on its release.

    The Linux 5.5 kernel update (dubbed “Kleptomaniac Octopus”) brings a host of performance tweaks as well as support for devices like the Raspberry Pi 4 and Broadcom chip BCM2711.

    Depending on your use of Linux the increasing support for Intel processor extensions for its x86-64 line could be of note, as the update includes Intel 5-level paging support as default. This has been done in preparation for the release of Intel servers that will have a significant amount of RAM.

Linux 5.5 released with enhanced hardware support

  • Linux 5.5 released with enhanced hardware support

    With this update, it seems clear that the main focus of the development team was to enhance the kernel’s hardware support. Other than that, there was also work done on improving the network driver and security.

    Delving deep into the hardware details, the new version will now be able to handle Raspberry Pi 4 better. Now, you will be able to connect your Raspberry Pi device to the Linux kernel right off the bat. Moreover, the kernel also offers better support for the Ugoos AM6, RK3308, and NanoPi Duo2 boards.

    The kernel will also come with drivers for Chromebook’s Wake-on-Voice feature, airplane mode LEDs, the keyboard backlight, and Fn key combinations.

    One impressive thing about this update is that it focuses on various demographics, even gamers. Accordingly, Linux 5.5 will be able to support two gaming keyboards, which include the first and second versions of Logitech G15. Although these keyboards are quite old, they are loved by gamers to this day, because they sport an LCD-screen, backlight modes, and macro buttons.

    Apart from that, gamers will have the ability to overclock their AMD OverDrive and also get better performance, all thanks to the improvements in the kernel’s scheduler.

    The developers of this update have also worked on improving the ext4, exFAT, and XFS file systems. When it comes to ext4, there is now support for direct I/O through fscrypt and iomap to handle smaller block sizes. Apart from that, users will also get better power management for Ice lake and Thunderbolt USB.

    Now coming to its upgraded security, it is now possible for MS Hyper-V virtual machines to hibernate and kernel concurrency sanitizer to spot data race conditions. Plus, from what we hear right now, Linux kernel 5.6 is highly likely to come with WireGuard support.

Linux 5.5 released, Bootlin contributions inside

  • Linux 5.5 released, Bootlin contributions inside

    Linux 5.5 was recently released, as usual bringing a large number of new features and improvements, which are nicely detailed in the LWN articles on merge window part 1 and merge window part 2, but also on the Kernelnewbies wiki.

    According to the statistics, a total of 14350 changes were made to this kernel release, to which Bootlin contributed 124 patches, making us the 19th contributing company by number of commits.

Some 5.5 kernel development statistics

  • Some 5.5 kernel development statistics

    The 5.5 kernel was released on January 26. Over the course of this development cycle, it was occasionally said that the holidays were slowing contributions. At the end, though, 5.5 saw the merging of 14,350 non-merge changesets from 1,885 developers — not exactly a slow-moving cycle. Indeed, 5.5 just barely edged out 5.4 as the kernel with the most developers ever. Read on for our traditional look at where the contributions to 5.5 came from, along with a digression into the stable-update process.

    Just under 590,000 lines of code were added for 5.5, while almost 272,000 were removed, for a net growth of 318,000 lines of code. Of the developers contributing to 5.5, 285 were contributing for the first time.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

GNU: GDB (Debugger), Project's History, and GCC (Compiler)

  • GDB Debugger Adds Support For Debuginfod Web Server

    Debuginfod is the Red Hat led debug information HTTP web server distributed as part of elfutils and able to supply on-demand source code and ELF/DWARF debug files to debuggers / IDEs / other compiler tooling. The GDB debugger can now tap debuginfod for on-demand source files and debug information that isn't present on the local system. The motivation with debuginfod is to carry less developer "baggage" on local systems when it comes to debug files and potentially even source files. Particularly for organizations or cases like Linux distributions, a centralized debuginfod server could in turn supply the needed files to clients based upon the requested build ID. Red Hat has been working to expand the debuginfod support both for the GNU toolchain and also LLVM, among other possible users.

  • When is GOTS not in the national interest?

    The modern open-source software (OSS) movement can be traced back to the early 1980s with the birth of Richard Stallman’s GNU Project and the Free Software Foundation. [...] However, cost is a red herring for the real challenge presented by GOTS software solutions. On the surface, GOTS seems very similar to OSS which implies that it has the larger structural advantages of OSS. If handled cautiously, it can have those advantages, but care needs to be taken about what sort of existing software is being commoditized. The U.S. has a national interest in maintaining a strong software development capability. We are fortunate to be the dominant software-building country in the world. According to the Forbes 2000 list, the total market capitalization of U.S. internet, software, and computer services companies is close to $4.7 trillion — more than twice the rest of the world combined. Software tech is an enormous comparative advantage for the U.S. As a result, it is clearly in the national interest to have the government avoid directly competing against and potentially weakening the U.S. private sector.

  • New compiler added to popular studio for ARM and Cortex-M IDE

    The studio for ARM/Cortex-M is now supplied with three different compilers: GCC, Clang and the company's own compiler. The new compiler outperforms GCC and regular Clang on most benchmarks, decreasing both size of generated code as well as its execution speed.

Kernel: LWN and Phoronix Articles About Latest Discussions and Linux Developments

  • Filesystem UID mapping for user namespaces: yet another shiftfs

    The idea of an ID-shifting virtual filesystem that would remap user and group IDs before passing requests through to an underlying real filesystem has been around for a few years but has never made it into the mainline. Implementations have taken the form of shiftfs and shifting bind mounts. Now there is yet another approach to the problem under consideration; this one involves a theoretically simpler approach that makes almost no changes to the kernel's filesystem layer at all. ID-shifting filesystems are meant to be used with user namespaces, which have a number of interesting characteristics; one of those is that there is a mapping between user IDs within the namespace and those outside of it. Normally this mapping is set up so that processes can run as root within the namespace without giving them root access on the system as a whole. A user namespace could be configured so that ID zero inside maps to ID 10000 outside, for example; ranges of IDs can be set up in this way, so that ID 20 inside would be 10020 outside. User namespaces thus perform a type of ID shifting now. In systems where user namespaces are in use, it is common to set them up to use non-overlapping ranges of IDs as a way of providing isolation between containers. But often complete isolation is not desired. James Bottomley's motivation for creating shiftfs was to allow processes within a user namespace to have root access to a specific filesystem. With the current patch set, instead, author Christian Brauner describes a use case where multiple containers have access to a shared filesystem and need to be able to access that filesystem with the same user and group IDs. Either way, the point is to be able to set up a mapping for user and group IDs that differs from the mapping established in the namespace itself.

  • Keeping secrets in memfd areas

    Back in November 2019, Mike Rapoport made the case that there is too much address-space sharing in Linux systems. This sharing can be convenient and good for performance, but in an era of advanced attacks and hardware vulnerabilities it also facilitates security problems. At that time, he proposed a number of possible changes in general terms; he has now come back with a patch implementing a couple of address-space isolation options for the memfd mechanism. This work demonstrates the sort of features we may be seeing, but some of the hard work has been left for the future. Sharing of address spaces comes about in a number of ways. Linux has traditionally mapped the kernel's address space into every user-space process; doing so improves performance in a number of ways. This sharing was thought to be secure for years, since the mapping doesn't allow user space to actually access that memory. The Meltdown and Spectre hardware bugs, though, rendered this sharing insecure; thus kernel page-table isolation was merged to break that sharing. Another form of sharing takes place in the processor's memory caches; once again, hardware vulnerabilities can expose data cached in this shared area. Then there is the matter of the kernel's direct map: a large mapping (in kernel space) that contains all of physical memory. This mapping makes life easy for the kernel, but it also means that all user-space memory is shared with the kernel. In other words, an attacker with even a limited ability to run code in the kernel context may have easy access to all memory in the system. Once again, in an era of speculative-execution bugs, that is not necessarily a good thing.

  • Revisiting stable-kernel regressions

    Stable-kernel updates are, unsurprisingly, supposed to be stable; that is why the first of the rules for stable-kernel patches requires them to be "obviously correct and tested". Even so, for nearly as long as the kernel community has been producing stable update releases, said community has also been complaining about regressions that make their way into those releases. Back in 2016, LWN did some analysis that showed the presence of regressions in stable releases, though at a rate that many saw as being low enough. Since then, the volume of patches showing up in stable releases has grown considerably, so perhaps the time has come to see what the situation with regressions is with current stable kernels. As an example of the number of patches going into the stable kernel updates, consider that, as of 4.9.213, 15,648 patches have been added to the original 4.9 release — that is an entire development cycle worth of patches added to a "stable" kernel. Reviewing all of those to see whether each contains a regression is not practical, even for the maintainers of the stable updates. But there is an automated way to get a sense for how many of those stable-update patches bring regressions with them. The convention in the kernel community is to add a Fixes tag to any patch fixing a bug introduced by another patch; that tag includes the commit ID for the original, buggy patch. Since stable kernel releases are supposed to be limited to fixes, one would expect that almost every patch would carry such a tag. In the real world, about 40-60% of the commits to a stable series carry Fixes tags; the proportion appears to be increasing over time as the discipline of adding those tags improves.

  • Finer-grained kernel address-space layout randomization

    The idea behind kernel address-space layout randomization (KASLR) is to make it harder for attackers to find code and data of interest to use in their attacks by loading the kernel at a random location. But a single random offset is used for the placement of the kernel text, which presents a weakness: if the offset can be determined for anything within the kernel, the addresses of other parts of the kernel are readily calculable. A new "finer-grained" KASLR patch set seeks to remedy that weakness for the text section of the kernel by randomly reordering the functions within the kernel code at boot time.

  • Debian discusses how to handle 2038

    At this point, most of the kernel work to avoid the year-2038 apocalypse has been completed. Said apocalypse could occur when time counted in seconds since 1970 overflows a 32-bit signed value (i.e. time_t). Work in the GNU C Library (glibc) and other C libraries is well underway as well. But the "fun" is just beginning for distributions, especially those that support 32-bit architectures, as a recent Debian discussion reveals. One of the questions is: how much effort should be made to support 32-bit architectures as they fade from use and 2038 draws nearer? Steve McIntyre started the conversation with a post to the debian-devel mailing list. In it, he noted that Arnd Bergmann, who was copied on the email, had been doing a lot of the work on the kernel side of the problem, but that it is mostly a solved problem for the kernel at this point. McIntyre and Bergmann (not to mention Debian as a whole) are now interested in what is needed to update a complete Linux system, such as Debian, to work with a 64-bit time_t. McIntyre said that glibc has been working on an approach that splits the problem up based on the architecture targeted. Those that already have a 64-bit time_t will simply have a glibc that works with that ABI. Others that are transitioning from a 32-bit time_t to the new ABI will continue to use the 32-bit version by default in glibc. Applications on the latter architectures can request the 64-bit time_t support from glibc, but then they (and any other libraries they use) will only get the 64-bit versions of the ABI. One thing that glibc will not be doing is bumping its SONAME (major version, essentially); doing so would make it easier to distinguish versions with and without the 64-bit support for 32-bit architectures. The glibc developers do not consider the change to be an ABI break, because applications have to opt into the change. It would be difficult and messy for Debian to change the SONAME for glibc on its own.

  • UEFI Boot Support Published For RISC-V On Linux

    As we've been expecting to happen with the Linux EFI code being cleaned up before the introduction of a new architecture, the RISC-V patches have been posted for bringing up UEFI boot support. Western Digital's Atish Patra sent out the patch series on Tuesday for adding UEFI support for the RISC-V architecture. This initial UEFI Linux bring-up is for supporting boot time services while the UEFI runtime service support is still being worked on. This RISC-V UEFI support can work in conjunction with the U-Boot bootloader and depends upon other recent Linux kernel work around RISC-V's Supervisor Binary Interface (SBI).

  • Linux Kernel Seeing Patches For NVIDIA's Proprietary Tegra Partition Table

    As an obstacle for upstreaming some particularly older NVIDIA Tegra devices (namely those running Android) is that they have GPT entry at the wrong location or lacking at all for boot support. That missing or botched GPT support is because those older devices make use of a NVIDIA proprietary/closed-source table format. As such, support for this proprietary NVIDIA Tegra Partition Table is being worked on for the Linux kernel to provide better upstream kernel support on these consumer devices. NVIDIA Tegra devices primarily rely on a special partition table format for their internal storage while some also support traditional GPT partitions. Those devices with non-flakey GPT support can boot fine but TegraPT support is being worked on for handling the upstream Linux kernel with the other devices lacking GPT support or where it's at the wrong sector. This issue primarily plagues Tegra 2 and Tegra 3 era hardware like some Google Nexus products (e.g. Nexus 7) while fortunately newer Tegra devices properly support GPT.

  • Intel Continues Bring-Up Of New Gateway SoC Architecture On Linux, ComboPHY Driver

    Besides all the usual hardware enablement activities with the usual names by Intel's massive open-source team working on the Linux kernel, one of the more peculiar bring-ups recently has been around the "Intel Gateway SoC" with more work abound for Linux 5.7. The Intel Gateway SoC is a seemingly yet-to-be-released product for high-speed network packet processing. The Gateway SoC supports the Intel Gateway Datapath Architecture (GWDPA) and is designed for very fast and efficient network processing. Outside of Linux kernel patches we haven't seen many Intel "Gateway" references to date. Gateway appears to be (or based on) the Intel "Lightning Mountain" SoC we were first to notice and bring attention to last summer when patches began appearing for that previously unknown codename.

Security: Updates, DNS Features in IPFire, Shodan and Canonical's Role in Robot Operating System (ROS 2)

  • Security updates for Wednesday

    Security updates have been issued by Debian (python-pysaml2), Mageia (clamav, graphicsmagick, opencontainers-runc, squid, and xmlsec1), Oracle (kernel, ksh, python-pillow, systemd, and thunderbird), Red Hat (rh-nodejs12-nodejs), Scientific Linux (ksh, python-pillow, and thunderbird), and SUSE (nodejs6, openssl, ppp, and squid).

  • What you can do with the new DNS features in IPFire

    Every time you try to access a website - for example ipfire.org - you will ask a DNS server for the IP address to connect to. They won't see anything past "the slash" in the URL, but that is not necessary to know what you probably have in mind to do. That DNS server now knows which bank you are with, where you work, where you do your online shopping, who is hosting your emails and many things more... Although this data is not too interesting about one individual, it becomes very relevant when you are looking at many profiles. People who shop at a certain place or are with a certain bank might be high earners. People who shop at another place might have trouble to stay afloat financially. Now I know what advertisements I need to show to which group so that they will become my customers. In short, your whole browser history tells a lot about you and you might be giving it away for free to the advertising industry or other parties who will use your data against you.

  • How Shodan Has Been Improved to Help Protect Energy Utilities

    Shodan is a well-known security hacking tool that has even been showcased on the popular Mr. Robot TV show. While Shodan can potentially be used by hackers, it can also be used for good to help protect critical infrastructure, including energy utilities. At the RSA Conference in San Francisco, Michael Mylrea, Director of Cybersecurity R&D (ICS, IoT, IIoT) at GE Global Research, led a session titled "Shodan 2.0: The World’s Most Dangerous Search Engine Goes on the Defensive," where he outlined how Shodan has been enabled to help utilities identify risks in critical energy infrastructure. Shodan, to the uninitiated, is a publicly available search engine tool that crawls the internet looking for publicly exposed devices. Mylrea explained that utilities are often resource constrained when it comes to cybersecurity and are typically unaware of their risk. In recent years, there have been a number of publicly disclosed incidents involving utilities. To help solve that challenge, Mylrea proposed a project to the US Department of Energy (DoE) to enhance Shodan for utilities so they could use the tool to find risks quickly.

  • Canonical takes leadership role in security for ROS

    Canonical is committed to the future of robotics, as proven a short time ago when we joined the Technical Steering Committee of the second version of the Robot Operating System (ROS 2). We’re also dedicated to building a foundation of enterprise-grade, industry leading security practices within Ubuntu, so we’re excited to join both of these strengths with our own Joe McManus taking the helm of the ROS 2 Security Working Group. We believe robots based on Linux are cheaper to develop, more flexible, faster to market, easier to manage, and more secure. While ROS began as an academic project over a decade ago, it has grown to become the most popular middleware for creating Linux-powered robots. It has harnessed the power of open source, allowing for many of the complex problems faced by robotics to be solved through collaboration. The ROS developer community has continued to grow, and ROS now enjoys an increasing amount of commercial use and supported robots. In response, the ROS community has completely overhauled the ROS codebase and started distributing ROS 2.

Audiocasts/Shows/Screencasts: The Linux Link Tech Show, FLOSS Weekly, Linux Headlines and Arch/Manjaro

  • The Linux Link Tech Show Episode 846

    nodejs 12, raspberry pi, 3d printing, air frying

  • FLOSS Weekly 567: DeepCode

    DeepCode alerts you about critical vulnerabilities you need to solve in your code. DeepCode finds critical vulnerabilities that other automated code reviews don't, such as Cross-Site Scripting, Path Traversal or SQL injection. DeepCode finds critical vulnerabilities that other automated code reviews don't, such as Cross-Site Scripting, Path Traversal or SQL injection with 90% precision.

  • 2020-02-26 | Linux Headlines

    Brave joins forces with the Wayback Machine, the Linux Foundation teams up with IBM to fight climate change, and The Document Foundation puts out a call to the community.

  • Linux Apps I Use At Work

    Linux Apps I Use At Work This video will go over all the applications I use on my Work PC. I go over my email, file browser, and many other features. As a life long Windows user, I was able to optimize my workflow once I moved to Linux and pick up a lot of productivity.

  • Manjaro 19.0 KDE Plasma Edition overview | #FREE OPERATING SYSTEM.

    In this video, I am going to show an overview of Manjaro Linux 19.0 KDE Plasma Edition and some of the applications pre-installed.

  • Manjaro 19.0 XFCE Run Through

    In this video, we are looking at Manjaro 19.0 XFCE.