Language Selection

English French German Italian Portuguese Spanish

Linux 4.13 Kernel Released

Filed under
Linux

Linus Torvalds has gone ahead and released the Linux 4.13 kernel.

As of writing, he hasn't yet published anything to the kernel mailing list but the new kernel can be fetched via Git.

Read more

Official message

  • Linux 4.13

    So last week was actually somewhat eventful, but not enough to push me
    to delay 4.13.

    Most of the changes since rc7 are actually networking fixes, the bulk
    of them to various drivers. With apologies to the authors of said
    patches, they don't look all that interesting (which is definitely
    exactly what you want just before a release). Details in the appended
    shortlog.

    Note that the shortlog below is obviously only since rc7 - the _full_
    4.13 log is much too big to post and nobody sane would read it. So if
    you're interested in all the rest of it, get the git tree and limit
    the logs to the files you are interested in if you crave details.

    No, the excitement was largely in the mmu notification layer, where we
    had a fairly last-minute regression and some discussion about the
    problem. Lots of kudos to Jérôme Glisse for jumping on it, and
    implementing the fix.

    What's nice to see is that the regression pointed out a nasty and not
    very well documented (or thought out) part of the mmu notifiers, and
    the fix not only fixed the problem, but did so by cleaning up and
    documenting what the right behavior should be, and furthermore did so
    by getting rid of the problematic notifier and actually removing
    almost two hundred lines in the process.

    I love seeing those kinds of fixes. Better, smaller, code.

    The other excitement this week was purely personal, consisting of
    seven hours of pure agony due to a kidney stone. I'm all good, but it
    sure _felt_ a lot longer than seven hours, and I don't even want to
    imagine what it is for people that have had the experience drag out
    for longer. Ugh.

    Anyway, on to actual 4.13 issues.

    While we've had lots of changes all over (4.13 was not particularly
    big, but even a "solidly average" release is not exactly small), one
    very _small_ change merits some extra attention, because it's one of
    those very rare changes where we change behavior due to security
    issues, and where people may need to be aware of that behavior change
    when upgrading.

    This time it's not really a kernel security issue, but a generic
    protocol security issue.

    The change in question is simply changing the default cifs behavior:
    instead of defaulting to SMB 1.0 (which you really should not use:
    just google for "stop using SMB1" or similar), the default cifs mount
    now defaults to a rather more modern SMB 3.0.

    Now, because you shouldn't have been using SMB1 anyway, this shouldn't
    affect anybody. But guess what? It almost certainly does affect some
    people, because they blithely continued using SMB1 without really
    thinking about it.

    And you certainly _can_ continue to use SMB1, but due to the default
    change, now you need to be *aware* of it. You may need to add an
    explicit "vers=1.0" to your mount options in /etc/fstab or similar if
    you *really* want SMB1.

    But if the new default of 3.0 doesn't work (because you still use a
    pterodactyl as a windshield wiper), before you go all the way back to
    the bad old days and use that "vers=1.0", you might want to try
    "vers=2.1". Because let's face it, SMB1 is just bad, bad, bad.

    Anyway, most people won't notice at all. And the ones that do notice
    can check their current situation (just look at the output of "mount"
    and see if you have any cifs things there), and you really should
    update from the default even if you are *not* upgrading kernels.

    Ok, enough about that. It was literally a two-liner change top
    defaults - out of the million or so lines of the full 4.13 patch
    changing real code.

    Go get the new kernel,

    Linus

  • The 4.13 kernel is out

    Linus has released the 4.13 kernel, right on schedule. Headline features in this release include kernel hardening via structure layout randomization, native TLS protocol support, better huge-page swapping, improved handling of writeback errors, better asynchronous I/O support, better power management via next-interrupt prediction, the elimination of the DocBook toolchain for formatted documentation, and more. There is one other change that is called out explicitly in the announcement: "The change in question is simply changing the default cifs behavior: instead of defaulting to SMB 1.0 (which you really should not use: just google for 'stop using SMB1' or similar), the default cifs mount now defaults to a rather more modern SMB 3.0."

Linux 4.13 release coverage

  • Linux Kernel 4.13 Released By Linus Torvalds — Here Are The Biggest Features

    Linux kernel 4.12 was released in early July, which was the second biggest release in terms of commits. It came with the support for new AMD Vega graphics support. Following Linux kernel 4.12, Linux boss Linus Torvalds has released Linux kernel 4.13 after seven release candidates.

    The Linux Kernel Mailing List announcement of kernel 4.13 turned out to be a little bit personal as Torvalds had to go through “seven hours of pure agony due to a kidney stone.” He expressed relief as kernel 4.13 wasn’t delayed.

  • Linus Torvalds passed a kidney stone and then squeezed out Linux 4.13

    Linus Torvalds has released Linux 4.13 to a waiting world and in so doing detailed a tricky work week in which he endured “seven hours of pure agony due to a kidney stone”.

    “I'm all good, but it sure _felt_ a lot longer than seven hours,” he wrote on the Linux Kernel Mailing List, “and I don't even want to imagine what it is for people that have had the experience drag out for longer. Ugh.”

    Far happier news is that this release of the Linux Kernel emerged after the seven release candidates to which Torvalds aspires.

Comment viewing options

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

More in Tux Machines

Debian Development and News

  • Freexian’s report about Debian Long Term Support, June 2018
    Like each month, here comes a report about the work of paid contributors to Debian LTS.
  • PKCS#11 v2.20
    By way of experiment, I've just enabled the PKCS#11 v2.20 implementation in the eID packages for Linux, but for now only in the packages in the "continuous" repository. In the past, enabling this has caused issues; there have been a few cases where Firefox would deadlock when PKCS#11 v2.20 was enabled, rather than the (very old and outdated) v2.11 version that we support by default. We believe we have identified and fixed all outstanding issues that caused such deadlocks, but it's difficult to be sure.
  • Plans for DebCamp and DebConf 18
    I recently became an active contributor to the Debian project, which has been consolidated throughout my GSoC project. In addition to the great learning with my mentors, Lucas Kanashiro and Raphäel Hertzog, the feedback from other community members has been very valuable to the progress we are making in the Distro Tracker. Tomorrow, thanks to Debian project sponsorship, I will take off for Hsinchu, Taiwan to attend DebCamp and DebConf18. It is my first DebConf and I’m looking forward to meeting new people from the Debian community, learn a lot and make useful contributions during the time I am there.
  • Building Debian packages in CI (ick)
    I develop a number of (fairly small) programs, as a hobby. Some of them I also maintain as packages in Debian. All of them I publish as Debian packages in my own APT repository. I want to make the process for making a release of any of my programs as easy and automated as possible, and that includes building Debian packages and uploading them to my personal APT repository, and to Debian itself.
  • My DebCamp/DebConf 18 plans
    Tomorrow I am going to another DebCamp and DebConf; this time at Hsinchu, Taiwan.
  • Things you can do with Debian: multimedia editing
    The Debian operating system serves many purposes and you can do amazing things with it. Apart of powering the servers behind big internet sites like Wikipedia and others, you can use Debian in your PC or laptop. I’ve been doing that for many years. One of the great things you can do is some multimedia editing. It turns out I love nature, outdoor sports and adventures, and I usually take videos and photos with my friends while doing such activities. And when I arrive home I love editing them for my other blog, or putting them together in a video.

32-Bit Vs. 64-Bit Operating System

This has really been confusing to some people choosing between 32-bit and 64-bit systems. Head over to any operating system’s website, you will be given a choice to download either versions of the same operating system. So what is the difference? Why do we have two different versions of the same OS? Let us solve this mystery here, once and for all. Read more

Convert video using Handbrake

Recently, when my son asked me to digitally convert some old DVDs of his high school basketball games, I immediately knew I would use Handbrake. It is an open source package that has all the tools necessary to easily convert video into formats that can be played on MacOS, Windows, Linux, iOS, Android, and other platforms. Handbrake is open source and distributable under the GPLv2 license. It's easy to install on MacOS, Windows, and Linux, including both Fedora and Ubuntu. In Linux, once it's installed, it can be launched from the command line with $ handbrake or selected from the graphical user interface. (In my case, that is GNOME 3.) Read more

today's howtos