linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Linux 5.10-rc1
Date: Sun, 25 Oct 2020 15:40:27 -0700	[thread overview]
Message-ID: <CAHk-=whcRFYSm0jj3Xh3xCyBaxCHA1ZMNO0h_gZso_WZFDUtiQ@mail.gmail.com> (raw)

Two weeks have passed, and the merge window is over. I've tagged and
pushed out 5.10-rc1, and everything looks fairly normal.

This looks to be a bigger release than I expected, and while the merge
window is smaller than the one for 5.8 was, it's not a *lot* smaller.
And 5.8 was our biggest release ever.

I'm not entirely sure whether this is just a general upward trend (we
did seem to plateau for a while there), or just a fluke, or perhaps
due to 5.9 dragging out an extra week. We will see, I guess.

That said, things seem to have gone fairly smoothly. I don't see any
huge red flags, and the merge window didn't cause any unusual issues
for me. Famous last words..

The most interesting - to me - change here is Christoph's setf_fs()
removal (it got merged through Al Viro, as you can see in my mergelog
below).  It's not a _huge_ change, but it's interesting because the
whole model of set_fs() to specify whether a userspace copy actually
goes to user space or kernel space goes back to pretty much the
original release of Linux, and while the name is entirely historic (it
hasn't used the %fs segment register in a long time), the concept has
remained. Until now.

We still do have "set_fs()" around, and not every architecture has
been converted to the new world order, but x86, powerpc, s390 and
RISC-V have had the address space overrides removed, and all the core
work is done. Other architectures will hopefully get converted away
from that very historic model too, but it might take a while to get
rid of it all.

Anyway, to most people that all shouldn't matter at all, and it's
mainly a small historical footnote that 5.10 no longer relies on the
whole set_fs() model. Most of the actual changes are - as usual -
driver updates, but there are changes all over. I think the merge log
below gives some kind of flavor of what's been going on on a high
level, but if you're interested in the details go look at the git
tree. As mentioned, it's a big merge window, with  almost 14k commits
(*) by closer to 1700 people.

Please go test,

                  Linus

(*) closer to 15k commits if you count merges.

---

Al Viro (6):
    copy_and_csum cleanups
    compat iovec cleanups
    compat quotactl cleanups
    compat mount cleanups
    initial set_fs() removal
    misc vfs updates

Alex Williamson (1):
    VFIO updates

Alexandre Belloni (1):
    RTC updates

Andreas Gruenbacher (1):
    gfs2 updates

Andrew Morton (3):
    misc updates
    more updates
    yet more updates

Anna Schumaker (1):
    NFS client updates

Arnaldo Carvalho de Melo (1):
    perf tools updates

Benson Leung (1):
    chrome platform updates

Bjorn Andersson (2):
    remoteproc updates
    rpmsg updates

Bjorn Helgaas (1):
    PCI updates

Boris Brezillon (1):
    i3c updates

Borislav Petkov (14):
    EDAC updates
    RAS updates
    x86 cpu updates
    x86 platform updates
    x86 PASID updates
    x86 fsgsbase updates
    x86 fpu updates
    x86 cleanups
    x86 cache resource control updates
    x86 fix
    x86 fixes
    x86 asm updates
    x86 SEV-ES support
    x86 SEV-ES fixes

Bruce Fields (1):
    nfsd updates

Casey Schaufler (1):
    smack updates

Christian Brauner (2):
    kernel_clone() updates
    pidfd updates

Christoph Hellwig (3):
    dma-mapping updates
    configfs updates
    dma-mapping fixes

Corey Minyard (1):
    IPMI updates

Damien Le Moal (1):
    zonefs updates

Daniel Lezcano (1):
    thermal updates

Daniel Thompson (1):
    kgdb updates

Darrick Wong (5):
    iomap updates
    xfs updates
    more xfs updates
    clone/dedupe/remap code refactoring
    xfs fixes

Dave Airlie (3):
    drm updates
    drm fixes
    more drm fixes

David Howells (1):
    afs updates

David Sterba (1):
    btrfs updates

David Teigland (1):
    dlm updates

Dmitry Torokhov (1):
    input updates

Dominique Martinet (1):
    9p updates

Eric Biggers (1):
    fscrypt updates

Gao Xiang (1):
    erofs updates

Geert Uytterhoeven (1):
    m68k updates

Greg KH (6):
    tty/serial updates
    driver core updates
    SPDX updates
    staging / IIO driver updates
    USB/PHY/Thunderbolt driver updates
    char/misc driver updates

Greg Ungerer (1):
    m68knommu updates

Guenter Roeck (1):
    hwmon updates

Hans de Goede (1):
    x86 platform driver updates

Helge Deller (2):
    parisc updates
    more parisc updates

Herbert Xu (1):
    crypto updates

Ilya Dryomov (1):
    ceph updates

Ingo Molnar (14):
    scheduler updates
    locking updates
    EFI changes
    orphan section checking
    static call support
    performance events updates
    perf/kprobes updates
    x86 kaslr updates
    x86 mm updates
    x86 build update
    x86 paravirt cleanup
    x86 Hyper-V update
    objtool updates
    RCU changes

Jaegeuk Kim (1):
    f2fs updates

Jakub Kicinski (2):
    networking updates
    networking fixes

James Bottomley (2):
    SCSI updates
    more SCSI updates

Jan Kara (2):
    UDF, reiserfs, ext2, quota fixes
    direct-io fix

Jarkko Sakkinen (1):
    tpm updates

Jason Gunthorpe (1):
    rdma updates

Jassi Brar (1):
    mailbox updates

Jean Delvare (1):
    dmi update

Jeff Layton (1):
    file locking fix

Jens Axboe (9):
    block updates
    io_uring updates
    libata updates
    block driver updates
    io_uring updates
    arch task_work cleanups
    libata fixes
    io_uring fixes
    block fixes

Jessica Yu (1):
    modules updates

Jiri Kosina (3):
    livepatching update
    HID updates
    trivial updates

Joerg Roedel (2):
    iommu updates
    iommu fix

Jon Mason (1):
    NTB fixes

Jonathan Corbet (2):
    documentation updates
    documentation fixes

Juergen Gross (3):
    xen updates
    more xen updates
    more xen updates

Julia Lawall (1):
    coccinelle updates

Kees Cook (2):
    seccomp updates
    overflow update

Konrad Rzeszutek Wilk (1):
    swiotlb updates

Lee Jones (2):
    MFD updates
    backlight updates

Linus Walleij (2):
    GPIO updates
    pin control updates

Mark Brown (3):
    regmap updates
    regulator updates
    spi updates

Masahiro Yamada (2):
    Kbuild updates
    Kconfig updates

Matthew Wilcox (1):
    XArray updates

Mauro Carvalho Chehab (2):
    media updates
    documentation updates

Micah Morton (1):
    SafeSetID updates

Michael Ellerman (2):
    powerpc updates
    powerpc fixes

Michael Tsirkin (1):
    virtio updates

Michal Simek (1):
    Microblaze build warning fix

Mike Snitzer (1):
    device mapper updates

Miklos Szeredi (2):
    overlayfs updates
    fuse updates

Mimi Zohar (1):
    integrity updates

Namjae Jeon (1):
    exfat updates

Olof Johansson (5):
    ARM SoC fixes
    ARM SoC platform updates
    ARM SoC-related driver updates
    ARM Devicetree updates
    ARM SoC defconfig updates

Palmer Dabbelt (2):
    RISC-V updates
    more RISC-V updates

Paolo Bonzini (2):
    KVM updates
    KVM fixes

Paul Moore (2):
    audit updates
    selinux updates

Pavel Machek (1):
    LED updates

Petr Mladek (2):
    printk updates
    printk fix

Rafael Wysocki (5):
    power management updates
    ACPI updates
    PNP updates
    more power management updates
    more ACPI updates

Richard Weinberger (4):
    MTD updates
    ubifs updates
    more ubi and ubifs updates
    UML updates

Rob Herring (1):
    devicetree updates

Russell King (1):
    ARM updates

Sebastian Reichel (1):
    power supply and reset updates

Shuah Khan (4):
    kselftest updates
    kselftest updates
    Kunit updates
    more Kunit updates

Stephen Boyd (1):
    clk updates

Steve French (2):
    cifs updates
    more cifs updates

Steven Rostedt (3):
    tracing updates
    tracing fix
    tracing ring-buffer fix

Takashi Iwai (2):
    sound updates
    sound fixes

Ted Ts'o (1):
    ext4 updates

Tejun Heo (1):
    cgroup updates

Tetsuo HandaL
 (1):
    tomoyo fix

Thierry Reding (1):
    pwm updates

Thomas Bogendoerfer (1):
    MIPS updates

Thomas Gleixner (9):
    debugobjects updates
    timekeeping updates
    irq updates
    x86 irq updates
    x86 entry code updates
    locking fix
    perf fix
    scheduler fixes
    timer fixes

Tony Luck (1):
    ia64 updates

Ulf Hansson (1):
    MMC updates

Vasily Gorbik (1):
    s390 updates

Vineet Gupta (2):
    ARC updates
    ARC fix

Vinod Koul (1):
    dmaengine updates

Wei Liu (2):
    Hyper-V updates
    another Hyper-V update

Will Deacon (2):
    arm64 updates
    more arm64 updates

Willy Tarreau (1):
    random32 updates

Wim Van Sebroeck (1):
    watchdog updates

Wolfram Sang (2):
    i2c updates
    i2c fix

             reply	other threads:[~2020-10-25 22:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 22:40 Linus Torvalds [this message]
2020-10-25 23:43 ` linux-next: stats Stephen Rothwell
2020-10-27  6:48 ` problems with splice from /proc (was Linux 5.10-rc1) Greg KH
2020-10-27  7:49   ` Christoph Hellwig
2020-10-27  7:55     ` Greg KH
2020-10-27  8:07       ` Christoph Hellwig
2020-10-27  8:14         ` Greg KH
2020-10-27  8:14           ` Christoph Hellwig
2020-10-27  9:17           ` Greg KH
2020-10-27 16:32             ` Christoph Hellwig
2020-10-27 17:43               ` Greg KH
2020-10-28 16:00               ` Greg KH
2020-10-28 18:33                 ` Greg KH
2020-10-28 18:34                   ` Christoph Hellwig
2020-10-28 18:35                   ` [PATCH] proc "single files": switch to ->read_iter Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHk-=whcRFYSm0jj3Xh3xCyBaxCHA1ZMNO0h_gZso_WZFDUtiQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).