|
|
Log in / Subscribe / Register

Brief items

Kernel development

Kernel release status

The 4.20 kernel was released on December 23; in the announcement Linus Torvalds said: "Let's face it, last week wasn't quite as quiet as I would have hoped for, but there really doesn't seem to be any point to delay 4.20 because everybody is already taking a break." Some of the headline features in 4.20 include network flow dissectors in BPF, the taprio traffic scheduler, peer-to-peer DMA support in the PCI layer, C-SKY architecture support, the pressure-stall instrumentation mechanism, the XArray data structure, and much more. The KernelNewbies 4.20 page has more information.

The 5.0 (probably) merge window is open, and a great deal of work has flowed into the mainline repository; see this article for a summary of what has been merged so far.

Stable updates: 4.19.12, 4.14.90, 4.9.147, 4.4.169, and 3.18.131 were released on December 21, followed by 4.19.13, 4.14.91, and 4.9.148 on December 29.

Comments (none posted)

Cook: Security things in Linux v4.20

Kees Cook summarizes the security-related improvements in the 4.20 kernel. "Enabling CONFIG_GCC_PLUGIN_STACKLEAK=y means almost all uninitialized variable flaws go away, with only a very minor performance hit (it appears to be under 1% for most workloads). It’s still possible that, within a single syscall, a later buggy function call could use 'uninitialized' bytes from the stack from an earlier function. Fixing this will need compiler support for pre-initialization (this is under development already for Clang, for example), but that may have larger performance implications."

Comments (13 posted)

Mourning Shaohua Li

The linux-kernel mailing list carries the sad news that Shaohua Li, a talented contributor to much of the core kernel and the maintainer of the MD RAID subsystem, passed away over the holidays. Thank you for your work, Shaohua, you will certainly be missed.

Full Story (comments: 14)

Quote of the week

The feature driven duct tape engineering mode is progressing massively. Proper root cause analysis has become the exception not the rule.

In our normal kernel development it's just annoying and eats up review capacity unnecessarily, but in the face of a timeline or real bugs it's worse. Aside of wasting time for review rounds, at some point other people have to just drop everything else and get it fixed.

Even if some people don't want to admit it, the increasing complexity of the hardware technology and as a consequence the increasing complexity of the kernel code base makes it mandatory to put correctness and maintainability first and not to fall for the featuritis and performance chants which are driving this industry. We've learned painfully what that causes in the last year.

Thomas Gleixner

Comments (none posted)

Distributions

Distribution quotes of the week

The following quotes are from the same Linux Journal article in which Bryan Lunduke talks with Debian Project Leader Chris Lamb, elementary OS founder Daniel Foré, and Fedora Project Leader Matthew Miller.

As long as there are a set of users who aren't getting their needs met by existing options, there's a purpose for any number of distros to exist. Some come and some go, and many are very very niche, but that's okay. I think there's a lot of people who are obsessed with trying to have some dominant player take a total monopoly, but in every other market category, it's immediately apparent how silly that idea is. You wouldn't want a single clothing manufacturer or a single restaurant chain or a single internet provider (wink hint nudge) to have total market dominance. Diversity and choice in the marketplace is good for customers, and I think it's no different when it comes to operating systems.
— Daniel Foré

Rushing to label this as a "good" or "bad" thing can make it easy to miss the underlying and more interesting lessons we can learn here.

Clearly, if everyone was using a Linux-based operating system, that would be a better state of affairs, but if we are overly quick to dismiss the usage of Mac systems as "bad", then we can often fail to understand why people have chosen to adopt the trade-offs of these platforms in the first place.

By not demonstrating sufficient empathy for such users as well as newcomers or those without our experience, we alienate potential users and contributors and tragically fail to communicate our true message. Basically, we can be our own worst enemy sometimes.

— Chris Lamb

Comments (none posted)

Development

Development quotes of the week

As with any other freedom, this kind does not come for free. I'm not talking about paying maintainers, though that seems to be what everyone else is fixated on of late. Freedoms are not won through money. Freedoms are won through the time of every free software developer. Unlike money, when time is spent it's gone forever; there's no chance to earn more later. Too many projects rely on the time of too few maintainers, and those maintainers are devoting too large of a slice of their lives to supporting the projects they love.
VM Brasseur

Even a hard-core, connected-appliances Luddite like myself is considering an IoT toaster oven now. I refuse to keep an Alexa in my house, and I don't want a Nest relaying my home's temperature back to Google. But sign me up for the dystopia where I one day get toast-doxxed. Breakfast is the most important meal of the day, and I want the world to know that I take it very seriously.
Megan Geuss (Thanks to Paul Wise)

Comments (1 posted)

Miscellaneous

Lawrence Roberts, Who Helped Design Internet’s Precursor, Dies at 81 (New York Times)

The New York Times reports the death of Dr. Lawrence G. Roberts, who was heavily involved in Arpanet. "Dr. Roberts was considered the decisive force behind packet switching, the technology that breaks data into discrete bundles that are then sent along various paths around a network and reassembled at their destination. He decided to use packet switching as the underlying technology of the Arpanet; it remains central to the function of the internet." (Thanks to Paul Wise.)

Comments (none posted)

Page editor: Jake Edge
Next page: Announcements>>


Copyright © 2019, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds