[1]: https://lkml.org/lkml/2019/3/31/256

[1]: https://lkml.org/lkml/2019/4/7/179

[1]: https://lkml.org/lkml/2019/4/14/265

[1]: https://lkml.org/lkml/2019/4/21/78

From the [announcement][1]:

> If rc6 was bigger than I wished, it really does seem to have been just
> due to timing of pull requests. Because rc7 is tiny.
>
> Just under half of the patch is various kinds of networking changes: a
> mix of core networking, network drivers and some netfilter selftests.
>
> The rest is mostly the usual architecture fixes, filesystems, and
> other drivers (mostly rdma and gpu). And misc random changes
> (Documentation, tracing, some mm fixlets).
>
> But it's all pretty tiny. Plus about 30% of the patches are marked for
> stable, so on the whole it really does feel like 5.1 is on target for
> a regular release next weekend.
>
> Knock wood.

[1]: https://lkml.org/lkml/2019/4/28/270

…x-5.1

[Announcement][1]:

> So it's a bit later in the day than I usually do this, just because I
> was waffling about the release. Partly because I got some small pull
> requests today, but mostly just because I wasn't looking forward to
> the timing of this upcoming 5.2 merge window.
>
> But the last-minute pull requests really weren't big enough to justify
> delaying things over, and hopefully the merge window timing won't be
> all that painful either. I just happen to have the college graduation
> of my oldest happen right smack dab in the middle of the upcoming
> merge window, so I might be effectively offline for a few days there.
> If worst comes to worst, I'll extend it to make it all work, but I
> don't think it will be needed.
>
> Anyway, on to 5.1 itself. The past week has been pretty calm, and the
> final patch from rc6 is not all that big. The shortlog is appended,
> but it's small changes all over. Networking, filesystem code, drivers,
> tooling, arch updates. Nothing particularly odd stands out.
>
> Of course, the shortlog below is just for that final calm week. On the
> whole, 5.1 looks very normal with just over 13k commits (plus another
> 1k+ if you count merges). Which is pretty much our normal size these
> days. No way to boil that down to a sane shortlog, with work all over.
>
> Go out and test,
>
>                 Linus

[1]: https://lkml.org/lkml/2019/5/5/278

Port commit 6cd982c (linux-4.19.37: Configure CGROUP_BPF) to
Linux 5.1.

> Configure CONFIG_BPF_SYSCALL and CONFIG_CGROUP_BPF, so that systemd
> services can use network filtering options. See
> `man systemd.resource-control`.
>
> This should avoid the warnings
>
>     systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support B
>     systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
>
> during boot.
>
> CONFIG_BPF_SYSCALL:
>
> Enable the bpf() system call that allows to manipulate eBPF
> programs and maps via file descriptors.
>
> CONFIG_CGROUP_BPF:
>
> Allow attaching eBPF programs to a cgroup using the bpf(2)
> syscall command BPF_PROG_ATTACH.
>
> In which context these programs are accessed depends on the type
> of attachment. For instance, programs that are attached using
> BPF_CGROUP_INET_INGRESS will be executed on the ingress path of
> inet sockets.

[Announcement][1]:

>  Makefile                               |    2
>  arch/arm64/include/asm/futex.h         |   55 ++-
>  drivers/acpi/acpi_lpss.c               |    4
>  drivers/bluetooth/hci_bcm.c            |   20 +
>  drivers/cpufreq/armada-37xx-cpufreq.c  |   22 +
>  drivers/hv/hv.c                        |    1
>  drivers/hwtracing/intel_th/pci.c       |    5
>  drivers/i3c/master.c                   |    5
>  drivers/iio/adc/qcom-spmi-adc5.c       |    1
>  drivers/scsi/lpfc/lpfc_attr.c          |  196 ++++++-------
>  drivers/scsi/lpfc/lpfc_ct.c            |   12
>  drivers/scsi/lpfc/lpfc_debugfs.c       |  474 ++++++++++++++++-----------------
>  drivers/scsi/lpfc/lpfc_debugfs.h       |    6
>  drivers/scsi/qla2xxx/qla_attr.c        |    4
>  drivers/scsi/qla2xxx/qla_nvme.c        |   19 -
>  drivers/scsi/qla2xxx/qla_target.c      |    4
>  drivers/soc/sunxi/Kconfig              |    1
>  drivers/staging/greybus/power_supply.c |    2
>  drivers/staging/most/cdev/cdev.c       |    2
>  drivers/staging/most/sound/sound.c     |    2
>  drivers/staging/wilc1000/wilc_netdev.c |    2
>  drivers/usb/class/cdc-acm.c            |   32 +-
>  drivers/usb/dwc3/Kconfig               |    6
>  drivers/usb/dwc3/core.c                |    2
>  drivers/usb/musb/Kconfig               |    2
>  drivers/usb/serial/f81232.c            |   39 ++
>  drivers/usb/storage/scsiglue.c         |   26 -
>  drivers/usb/storage/uas.c              |   35 +-
>  include/net/bluetooth/hci_core.h       |    3
>  kernel/futex.c                         |  188 ++++++++-----
>  kernel/irq/manage.c                    |    4
>  lib/ubsan.c                            |   49 +--
>  net/bluetooth/hci_conn.c               |    8
>  net/bluetooth/hidp/sock.c              |    1
>  net/bluetooth/l2cap_core.c             |    9
>  sound/soc/intel/common/sst-firmware.c  |    8
>  36 files changed, 715 insertions(+), 536 deletions(-)

[1]: https://lkml.org/lkml/2019/5/11/29

Fixes: #1102

[Announcement][1]:

> I'm announcing the release of the 5.1.2 kernel.
>
> All users of the 5.1 kernel series must upgrade.  Well, kind of, let me rephrase that...
>
> All users of Intel processors made since 2011 must upgrade.
>
> Note, this release, and the other stable releases that are all being
> released right now at the same time, just went out all contain patches
> that have only seen the "public eye" for about 5 minutes.  So be
> forwarned, they might break things, they might not build, but hopefully
> they fix things.  Odds are we will be fixing a number of small things in
> this area for the next few weeks as things shake out on real hardware
> and workloads.  So don't think you are done updating your kernel, you
> never are done with that :)
>
> As for what specifically these changes fix, I'll let the tech news sites
> fill you in on the details.  Or go read the excellently written Xen
> Security Advisory 297:
> 	https://xenbits.xen.org/xsa/advisory-297.html
> That should give you a good idea of what a number of people have been
> dealing with for many many many months now.
>
> Many thanks goes out to Thomas Gleixner for going above and beyond to do
> the backports to the 5.1, 5.0, 4.19, and 4.14 kernel trees, and to Ben
> Hutchings for doing the 4.9 work.  And of course to all of the
> developers who have been working on this in secret and doing reviews of
> the many different proposals and versions of the patches.
>
> As I said before just over a year ago, Intel once again owes a bunch of
> people a lot of drinks for fixing their hardware bugs, in our
> software...
>
> Anyway, as usual, the updated 5.1.y git tree can be found at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.1.y
> and can be browsed at the normal kernel.org git web browser:
> 	https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary

[1]: https://lkml.org/lkml/2019/5/14/651

[1]: https://lkml.org/lkml/2019/5/17/104

Linux 5.2-rc1 [1] is available, so remove the 5.1 Linux kernels, never
installed on the distmaster – especially as the proprietary Nvidia
driver was not packaged.

[1]: https://lkml.org/lkml/2019/5/19/119