Bug #1814874 “NULL pointer dereference when using z3fold and zsw...” : Bugs : linux package : Ubuntu

Revision history for this message

In Linux Kernel Bug Tracker #201603, jagannathante (jagannathante-linux-kernel-bugs) wrote on 2018-11-02:

#2

Created attachment 279297
dmesg log of crash

This happens mostly during memory pressure but I am not sure how to trigger it reliably. I am attaching the full log.

This is the kernel commandline

>BOOT_IMAGE=../vmlinuz-linux root=UUID=57274b3a-92ab-468e-b03a-06026675c1af rw
>rd.luks.name=92b4aeb2-fb97-45c1-8a60-2816efe5d57e=home resume=/dev/mapper/home
>resume_offset=42772480 acpi_backlight=video zswap.enabled=1 zswap.zpool=z3fold
>zswap.max_pool_percent=5 transparent_hugepage=madvise scsi_mod.use_blk_mq=1
>vga=current initrd=../intel-ucode.img,../initramfs-linux.img

I found this bug https://bugzilla.kernel.org/show_bug.cgi?id=198585 to be very similar but the proposed fix has not been merged so I can't be sure if it will fix the issue I am having.

Revision history for this message

In Linux Kernel Bug Tracker #201603, enelar (enelar-linux-kernel-bugs) wrote on 2018-11-06:

#3

Created attachment 279341
Log before kernel panic and after hard reset

Arch+deepin+systemd-swap

zswap_enabled=1
zswap_compressor=lzo
zswap_max_pool_percent=5
zswap_zpool=z3fold

zram_enabled=1
zram_size=$(($RAM_SIZE*1/10))
zram_streams=$NCPU
zram_alg=lz4
zram_prio=32767

Revision history for this message

In Linux Kernel Bug Tracker #201603, akpm (akpm-linux-kernel-bugs) wrote on 2018-11-06:

#4

(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Fri, 02 Nov 2018 10:41:46 +0000 <email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=201603
>
> Bug ID: 201603
> Summary: NULL pointer dereference when using z3fold and zswap
> Product: Memory Management
> Version: 2.5
> Kernel Version: 4.18.16
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Page Allocator
> Assignee: <email address hidden>
> Reporter: <email address hidden>
> Regression: No
>
> Created attachment 279297
> --> https://bugzilla.kernel.org/attachment.cgi?id=279297&action=edit
> dmesg log of crash
>
> This happens mostly during memory pressure but I am not sure how to trigger
> it
> reliably. I am attaching the full log.
>
> This is the kernel commandline
>
> >BOOT_IMAGE=../vmlinuz-linux root=UUID=57274b3a-92ab-468e-b03a-06026675c1af
> rw
> >rd.luks.name=92b4aeb2-fb97-45c1-8a60-2816efe5d57e=home
> resume=/dev/mapper/home
> >resume_offset=42772480 acpi_backlight=video zswap.enabled=1
> zswap.zpool=z3fold
> >zswap.max_pool_percent=5 transparent_hugepage=madvise scsi_mod.use_blk_mq=1
> >vga=current initrd=../intel-ucode.img,../initramfs-linux.img
>
> I found this bug https://bugzilla.kernel.org/show_bug.cgi?id=198585 to be
> very
> similar but the proposed fix has not been merged so I can't be sure if it
> will
> fix the issue I am having.
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

Revision history for this message

In Linux Kernel Bug Tracker #201603, vitalywool (vitalywool-linux-kernel-bugs) wrote on 2018-11-06:

#5

Created attachment 279353
attachment-22937-0.html

Hi,
Den tis 6 nov. 2018 kl 22:48 skrev Andrew Morton <<email address hidden>
>:

>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Fri, 02 Nov 2018 10:41:46 +0000 <email address hidden>
> wrote:
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=201603
> >
> > Bug ID: 201603
> > Summary: NULL pointer dereference when using z3fold and zswap
> > Product: Memory Management
> > Version: 2.5
> > Kernel Version: 4.18.16
> > Hardware: All
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: high
> > Priority: P1
> > Component: Page Allocator
> > Assignee: <email address hidden>
> > Reporter: <email address hidden>
> > Regression: No
> >
> > Created attachment 279297
> > --> https://bugzilla.kernel.org/attachment.cgi?id=279297&action=edit
> > dmesg log of crash
>
>
Basing on what I see in dmesg, it is highly likely to get fixed by
https://lkml.org/lkml/2018/11/5/726. Could you please apply/retest?

Best regards,
Vitaly

> > This happens mostly during memory pressure but I am not sure how to
> trigger it
> > reliably. I am attaching the full log.
> >
> > This is the kernel commandline
> >
> > >BOOT_IMAGE=../vmlinuz-linux
> root=UUID=57274b3a-92ab-468e-b03a-06026675c1af rw
> > >rd.luks.name=92b4aeb2-fb97-45c1-8a60-2816efe5d57e=home
> resume=/dev/mapper/home
> > >resume_offset=42772480 acpi_backlight=video zswap.enabled=1
> zswap.zpool=z3fold
> > >zswap.max_pool_percent=5 transparent_hugepage=madvise
> scsi_mod.use_blk_mq=1
> > >vga=current initrd=../intel-ucode.img,../initramfs-linux.img
> >
> > I found this bug https://bugzilla.kernel.org/show_bug.cgi?id=198585 to
> be very
> > similar but the proposed fix has not been merged so I can't be sure if
> it will
> > fix the issue I am having.
> >
> > --
> > You are receiving this mail because:
> > You are the assignee for the bug.
>

Created attachment 279353
attachment-22937-0.html

Hi,
Den tis 6 nov. 2018 kl 22:48 skrev Andrew Morton <akpm@linux-foundation.org
>:

>
> (switched to email.  Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Fri, 02 Nov 2018 10:41:46 +0000 bugzilla-daemon@bugzilla.kernel.org
> wrote:
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=201603
> >
> >             Bug ID: 201603
> >            Summary: NULL pointer dereference when using z3fold and zswap
> >            Product: Memory Management
> >            Version: 2.5
> >     Kernel Version: 4.18.16
> >           Hardware: All
> >                 OS: Linux
> >               Tree: Mainline
> >             Status: NEW
> >           Severity: high
> >           Priority: P1
> >          Component: Page Allocator
> >           Assignee: akpm@linux-foundation.org
> >           Reporter: jagannathante@gmail.com
> >         Regression: No
> >
> > Created attachment 279297
> >   --> https://bugzilla.kernel.org/attachment.cgi?id=279297&action=edit
> > dmesg log of crash
>
>
Basing on what I see in dmesg, it is highly likely to get fixed by
https://lkml.org/lkml/2018/11/5/726. Could you please apply/retest?

Best regards,
   Vitaly

> > This happens mostly during memory pressure but I am not sure how to
> trigger it
> > reliably. I am attaching the full log.
> >
> > This is the kernel commandline
> >
> > >BOOT_IMAGE=../vmlinuz-linux
> root=UUID=57274b3a-92ab-468e-b03a-06026675c1af rw
> > >rd.luks.name=92b4aeb2-fb97-45c1-8a60-2816efe5d57e=home
> resume=/dev/mapper/home
> > >resume_offset=42772480 acpi_backlight=video zswap.enabled=1
> zswap.zpool=z3fold
> > >zswap.max_pool_percent=5 transparent_hugepage=madvise
> scsi_mod.use_blk_mq=1
> > >vga=current initrd=../intel-ucode.img,../initramfs-linux.img
> >
> > I found this bug https://bugzilla.kernel.org/show_bug.cgi?id=198585 to
> be very
> > similar but the proposed fix has not been merged so I can't be sure if
> it will
> > fix the issue I am having.
> >
> > --
> > You are receiving this mail because:
> > You are the assignee for the bug.
>

Revision history for this message

In Linux Kernel Bug Tracker #201603, enelar (enelar-linux-kernel-bugs) wrote on 2018-11-07:

#6

Created attachment 279367
attachment-27234-0.html

Additional to original report I have
kernel BUG at mm/zswap.c:1175
(please take a look at my log)
Will test patch tomorrow

On Wed, Nov 7, 2018, 1:10 AM <<email address hidden> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=201603
>
> --- Comment #3 from Vitaly (<email address hidden>) ---
> Hi,
> Den tis 6 nov. 2018 kl 22:48 skrev Andrew Morton <
> <email address hidden>
> >:
>
> >
> > (switched to email. Please respond via emailed reply-to-all, not via the
> > bugzilla web interface).
> >
> > On Fri, 02 Nov 2018 10:41:46 +0000 <email address hidden>
> > wrote:
> >
> > > https://bugzilla.kernel.org/show_bug.cgi?id=201603
> > >
> > > Bug ID: 201603
> > > Summary: NULL pointer dereference when using z3fold and
> zswap
> > > Product: Memory Management
> > > Version: 2.5
> > > Kernel Version: 4.18.16
> > > Hardware: All
> > > OS: Linux
> > > Tree: Mainline
> > > Status: NEW
> > > Severity: high
> > > Priority: P1
> > > Component: Page Allocator
> > > Assignee: <email address hidden>
> > > Reporter: <email address hidden>
> > > Regression: No
> > >
> > > Created attachment 279297
> > > --> https://bugzilla.kernel.org/attachment.cgi?id=279297&action=edit
> > > dmesg log of crash
> >
> >
> Basing on what I see in dmesg, it is highly likely to get fixed by
> https://lkml.org/lkml/2018/11/5/726. Could you please apply/retest?
>
> Best regards,
> Vitaly
>
> > > This happens mostly during memory pressure but I am not sure how to
> > trigger it
> > > reliably. I am attaching the full log.
> > >
> > > This is the kernel commandline
> > >
> > > >BOOT_IMAGE=../vmlinuz-linux
> > root=UUID=57274b3a-92ab-468e-b03a-06026675c1af rw
> > > >rd.luks.name=92b4aeb2-fb97-45c1-8a60-2816efe5d57e=home
> > resume=/dev/mapper/home
> > > >resume_offset=42772480 acpi_backlight=video zswap.enabled=1
> > zswap.zpool=z3fold
> > > >zswap.max_pool_percent=5 transparent_hugepage=madvise
> > scsi_mod.use_blk_mq=1
> > > >vga=current initrd=../intel-ucode.img,../initramfs-linux.img
> > >
> > > I found this bug https://bugzilla.kernel.org/show_bug.cgi?id=198585 to
> > be very
> > > similar but the proposed fix has not been merged so I can't be sure if
> > it will
> > > fix the issue I am having.
> > >
> > > --
> > > You are receiving this mail because:
> > > You are the assignee for the bug.
> >
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Created attachment 279367
attachment-27234-0.html

Additional to original report I have
kernel BUG at mm/zswap.c:1175
(please take a look at my log)
Will test patch tomorrow

On Wed, Nov 7, 2018, 1:10 AM <bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=201603
>
> --- Comment #3 from Vitaly (vitalywool@gmail.com) ---
> Hi,
> Den tis 6 nov. 2018 kl 22:48 skrev Andrew Morton <
> akpm@linux-foundation.org
> >:
>
> >
> > (switched to email.  Please respond via emailed reply-to-all, not via the
> > bugzilla web interface).
> >
> > On Fri, 02 Nov 2018 10:41:46 +0000 bugzilla-daemon@bugzilla.kernel.org
> > wrote:
> >
> > > https://bugzilla.kernel.org/show_bug.cgi?id=201603
> > >
> > >             Bug ID: 201603
> > >            Summary: NULL pointer dereference when using z3fold and
> zswap
> > >            Product: Memory Management
> > >            Version: 2.5
> > >     Kernel Version: 4.18.16
> > >           Hardware: All
> > >                 OS: Linux
> > >               Tree: Mainline
> > >             Status: NEW
> > >           Severity: high
> > >           Priority: P1
> > >          Component: Page Allocator
> > >           Assignee: akpm@linux-foundation.org
> > >           Reporter: jagannathante@gmail.com
> > >         Regression: No
> > >
> > > Created attachment 279297
> > >   --> https://bugzilla.kernel.org/attachment.cgi?id=279297&action=edit
> > > dmesg log of crash
> >
> >
> Basing on what I see in dmesg, it is highly likely to get fixed by
> https://lkml.org/lkml/2018/11/5/726. Could you please apply/retest?
>
> Best regards,
>    Vitaly
>
> > > This happens mostly during memory pressure but I am not sure how to
> > trigger it
> > > reliably. I am attaching the full log.
> > >
> > > This is the kernel commandline
> > >
> > > >BOOT_IMAGE=../vmlinuz-linux
> > root=UUID=57274b3a-92ab-468e-b03a-06026675c1af rw
> > > >rd.luks.name=92b4aeb2-fb97-45c1-8a60-2816efe5d57e=home
> > resume=/dev/mapper/home
> > > >resume_offset=42772480 acpi_backlight=video zswap.enabled=1
> > zswap.zpool=z3fold
> > > >zswap.max_pool_percent=5 transparent_hugepage=madvise
> > scsi_mod.use_blk_mq=1
> > > >vga=current initrd=../intel-ucode.img,../initramfs-linux.img
> > >
> > > I found this bug https://bugzilla.kernel.org/show_bug.cgi?id=198585 to
> > be very
> > > similar but the proposed fix has not been merged so I can't be sure if
> > it will
> > > fix the issue I am having.
> > >
> > > --
> > > You are receiving this mail because:
> > > You are the assignee for the bug.
> >
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Revision history for this message

In Linux Kernel Bug Tracker #201603, imwellcushtymelike (imwellcushtymelike-linux-kernel-bugs) wrote on 2019-02-06:

#7

Any update on this and does anyone know if this is a regression?

Revision history for this message

Ken Sharp (kennybobs) wrote on 2019-02-06:

#1

dmesg.txt Edit (12.6 KiB, text/plain)
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (965 bytes, text/plain; charset="utf-8")

no longer affects:

systemd

Bug Watch Updater (bug-watch-updater) on 2019-02-06

Changed in linux:
importance:	Unknown → High
status:	Unknown → Confirmed

Revision history for this message

In Linux Kernel Bug Tracker #201603, imwellcushtymelike (imwellcushtymelike-linux-kernel-bugs) wrote on 2019-02-12:

#8

This seems related from Chrome OS:
https://bugs.chromium.org/p/chromium/issues/detail?id=822360

I'm afraid that I don't currently have the resources to test the patches (that haven't been committed upstream) at the moment, although I may need to in the end as one of my servers is crashing every day.

Revision history for this message

In Linux Kernel Bug Tracker #201603, vitalywool (vitalywool-linux-kernel-bugs) wrote on 2019-02-21:

#9

Wait a second, you are sitting on a discontinued kernel. The fix has gone in back in December. Upgrade to longterm series, it's there since 4.19.6, and retest. Otherwise I do suggest that we close this issue.

Revision history for this message

In Linux Kernel Bug Tracker #201603, jagannathante (jagannathante-linux-kernel-bugs) wrote on 2019-02-21:

#10

I am going to enable zswap and z3fold to confirm the fix. Sorry, I didn't follow through after it was merged.

Revision history for this message

In Linux Kernel Bug Tracker #201603, imwellcushtymelike (imwellcushtymelike-linux-kernel-bugs) wrote on 2019-02-21:

#11

I'm installing it too. I didn't know there was a fix in-place anywhere so this is good news! It'll take me a few days of testing to get a result.

Revision history for this message

In Linux Kernel Bug Tracker #201603, jagannathante (jagannathante-linux-kernel-bugs) wrote on 2019-03-04:

#12

I can confirm there have been no crashes since I switched, so closing. Thanks for the help and fix :)

Bug Watch Updater (bug-watch-updater) on 2019-03-04

Changed in linux:
status:	Confirmed → Fix Released

Revision history for this message

Ken Sharp (kennybobs) wrote on 2019-03-04:

#13

As above: this should be fixed in Disco, though I have only just switched to the upstream kernel for testing, I suspect that Jagannathan's testing is correct.

This is a very serious stability issue in the Ubuntu kernel and really should have had some sort of interaction here by now. It is probably being avoided in the wild by scaling busy systems, but that's not an option for everyone.

tags:

added: kernel-fixed-upstream
removed: kernel-bug-exists-upstream

Revision history for this message

Ken Sharp (kennybobs) wrote on 2019-03-04:

#14

As an aside: I'm seeing much better system response time using zRAM alone than I am using zswap alone, but this may have improved in the newer kernel. In both cases though I am using KSM and THP which clearly improve memory use.

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-04-02:

#15

Fix available in upstream:
https://github.com/torvalds/linux/commit/ca0246bb97c23da9d267c2107c07fb77e38205c9

It can be cherry-picked into B/C

It's already landed in Disco as Ken mentioned in #13

affects:

linux-signed-hwe (Ubuntu) → linux (Ubuntu)

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-04-03:

#16

Hello Ken,

do you have a command to reproduce this? I would like to use it to verify the fix.

I tired this on a Cosmic KVM allocated with 2G ram, 512MB swap, with:
* "zswap.enabled=1 zswap.zpool=z3fold zswap.max_pool_percent=5 zswap.compressor=lz4" added to the grub
* z3pool, lz4, lz4_compress module added to initramfs

and stress it with the stress command with 115% of available memory.

stress --vm-bytes $(awk '/MemAvailable/{printf "%d\n", $2 * 1.15;}' < /proc/meminfo)k --vm-keep -m 1

All I got is a soft CPU lockup. Or should I leave it there for a while?
Thanks

Revision history for this message

Ken Sharp (kennybobs) wrote on 2019-04-03:

#17

I don't recall seeing a soft lockup at all, not a related one anyway. Sadly I don't have a specific command but I did find it triggered when:

1. Memory is overcommited. It doesn't have to be heavily overcommitted.
2. I/O is very high.
3. I “leave“ an SSH session, releasing a small amount of memory.

The patch seems to suggest that it is this release that causes the problem. My guess would be that part of the session is already in the compressed cache, and it is released while another process attempts to enter the compressed cache. I don't even know if that makes sense.

To add to the confusion: it crashes fairly consistently across VMs and bare metal, but occasionally a server under the same sort of stress, and otherwise identical setup, can run weeks or months without issue.

At this point, though, I know of no specific command to trigger it. If I get time I can have a play around but that may never happen.

I usually have zswap.max_pool_percent=50, but everything else can vary and the result is the same.

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-04-09:

#18

Thanks for the feedback, I will see if I can reproduce this and SRU this patch.

Changed in linux (Ubuntu):
assignee:	nobody → Po-Hsu Lin (cypressyew)
status:	New → In Progress

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-04-12:

#19

Can be reproduced easily with Cosmic kernel, patch works as expected. A test kernel could be found here: http://people.canonical.com/~phlin/kernel/lp-1814874-z3fold-zswap/Cosmic/

Will try this on Bionic next.

Po-Hsu Lin (cypressyew) on 2019-04-12

Changed in linux (Ubuntu Bionic):
status:	New → In Progress
Changed in linux (Ubuntu Cosmic):
status:	New → In Progress
Changed in linux (Ubuntu):
status:	In Progress → Fix Released
tags:	added: cosmic

Po-Hsu Lin (cypressyew) on 2019-04-17

description:

updated

Kleber Sacilotto de Souza (kleber-souza) on 2019-04-23

Changed in linux (Ubuntu Cosmic):
status:	In Progress → Fix Committed
Changed in linux (Ubuntu Bionic):
status:	In Progress → Fix Committed

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2019-04-25:

#20

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed-cosmic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: verification-needed-cosmic

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2019-04-29:

#21

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags:

added: verification-needed-bionic

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-05-08:

#22

Bionic VM with proposed kernel withstand the stress for over an hour.

tags:

added: verification-done-bionic
removed: verification-needed-bionic

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-05-08:

#23

Cosmic verification in progress.

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2019-05-09:

#24

Cosmic VM with proposed kernel withstand the stress for over 12 hours.

tags:

added: verification-done-cosmic
removed: verification-needed-cosmic

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-05-14:

#25

Download full text (12.6 KiB)

This bug was fixed in the package linux - 4.15.0-50.54

---------------
linux (4.15.0-50.54) bionic; urgency=medium

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
    - Documentation/l1tf: Fix small spelling typo
    - x86/cpu: Sanitize FAM6_ATOM naming
    - kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
    - locking/atomics, asm-generic: Move some macros from <linux/bitops.h> to a
      new <linux/bits.h> file
    - tools include: Adopt linux/bits.h
    - x86/msr-index: Cleanup bit defines
    - x86/speculation: Consolidate CPU whitelists
    - x86/speculation/mds: Add basic bug infrastructure for MDS
    - x86/speculation/mds: Add BUG_MSBDS_ONLY
    - x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
    - x86/speculation/mds: Add mds_clear_cpu_buffers()
    - x86/speculation/mds: Clear CPU buffers on exit to user
    - x86/kvm/vmx: Add MDS protection when L1D Flush is not active
    - x86/speculation/mds: Conditionally clear CPU buffers on idle entry
    - x86/speculation/mds: Add mitigation control for MDS
    - x86/speculation/mds: Add sysfs reporting for MDS
    - x86/speculation/mds: Add mitigation mode VMWERV
    - Documentation: Move L1TF to separate directory
    - Documentation: Add MDS vulnerability documentation
    - x86/speculation/mds: Add mds=full,nosmt cmdline option
    - x86/speculation: Move arch_smt_update() call to after mitigation decisions
    - x86/speculation/mds: Add SMT warning message
    - x86/speculation/mds: Fix comment
    - x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
    - x86/speculation/mds: Add 'mitigations=' support for MDS

* CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option

* CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option

  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
    CVE-2018-3646
    - cpu/speculation: Add 'mitigations=' cmdline option
    - x86/speculation: Support 'mitigations=' cmdline option

* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux (4.15.0-49.53) bionic; urgency=medium

* linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)

  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
    (required for POWER9 DD2.3) (LP: #1822870)
    - powerpc/64s: Add support for ori barrier_nospec patching
    - powerpc/64s: Patch barrier_nospec in modules
    - powerpc/64s: Enable barrier_nospec based on firmware settings
    - powerpc: Use barrier_nospec in copy_from_user()
    - powerpc/64: Use barrier_nospec in syscall entry
    - powerpc/64s: Enhance the information in cpu_show_spectre_v1()
    - powerpc/64: Disable the speculation barrier from the command line
    - powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
    - powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
    - powerpc/64: Call setup_barrier_nospec() from setup_arch()
    - powerpc/64: Make meltdown reporting Book3S 64 specific
    - powerpc/lib/code-patching: refactor patch_instruction()
    - powerpc/lib/feature-fixups: use raw_patch_instruction()
    - powerpc/asm: Add a patch_site mac...

This bug was fixed in the package linux - 4.15.0-50.54

---------------
linux (4.15.0-50.54) bionic; urgency=medium

* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
    - Documentation/l1tf: Fix small spelling typo
    - x86/cpu: Sanitize FAM6_ATOM naming
    - kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
    - locking/atomics, asm-generic: Move some macros from <linux/bitops.h> to a
      new <linux/bits.h> file
    - tools include: Adopt linux/bits.h
    - x86/msr-index: Cleanup bit defines
    - x86/speculation: Consolidate CPU whitelists
    - x86/speculation/mds: Add basic bug infrastructure for MDS
    - x86/speculation/mds: Add BUG_MSBDS_ONLY
    - x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
    - x86/speculation/mds: Add mds_clear_cpu_buffers()
    - x86/speculation/mds: Clear CPU buffers on exit to user
    - x86/kvm/vmx: Add MDS protection when L1D Flush is not active
    - x86/speculation/mds: Conditionally clear CPU buffers on idle entry
    - x86/speculation/mds: Add mitigation control for MDS
    - x86/speculation/mds: Add sysfs reporting for MDS
    - x86/speculation/mds: Add mitigation mode VMWERV
    - Documentation: Move L1TF to separate directory
    - Documentation: Add MDS vulnerability documentation
    - x86/speculation/mds: Add mds=full,nosmt cmdline option
    - x86/speculation: Move arch_smt_update() call to after mitigation decisions
    - x86/speculation/mds: Add SMT warning message
    - x86/speculation/mds: Fix comment
    - x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
    - x86/speculation/mds: Add 'mitigations=' support for MDS

* CVE-2017-5715 // CVE-2017-5753
    - s390/speculation: Support 'mitigations=' cmdline option

* CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
    - powerpc/speculation: Support 'mitigations=' cmdline option

* CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
    CVE-2018-3646
    - cpu/speculation: Add 'mitigations=' cmdline option
    - x86/speculation: Support 'mitigations=' cmdline option

* Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log

linux (4.15.0-49.53) bionic; urgency=medium

* linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)

* Backport support for software count cache flush Spectre v2 mitigation. (CVE)
    (required for POWER9 DD2.3) (LP: #1822870)
    - powerpc/64s: Add support for ori barrier_nospec patching
    - powerpc/64s: Patch barrier_nospec in modules
    - powerpc/64s: Enable barrier_nospec based on firmware settings
    - powerpc: Use barrier_nospec in copy_from_user()
    - powerpc/64: Use barrier_nospec in syscall entry
    - powerpc/64s: Enhance the information in cpu_show_spectre_v1()
    - powerpc/64: Disable the speculation barrier from the command line
    - powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
    - powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
    - powerpc/64: Call setup_barrier_nospec() from setup_arch()
    - powerpc/64: Make meltdown reporting Book3S 64 specific
    - powerpc/lib/code-patching: refactor patch_instruction()
    - powerpc/lib/feature-fixups: use raw_patch_instruction()
    - powerpc/asm: Add a patch_site macro & helpers for patching instructions
    - powerpc/64s: Add new security feature flags for count cache flush
    - powerpc/64s: Add support for software count cache flush
    - powerpc/pseries: Query hypervisor for count cache flush settings
    - powerpc/powernv: Query firmware for count cache flush settings
    - powerpc/fsl: Add nospectre_v2 command line argument
    - KVM: PPC: Book3S: Add count cache flush parameters to kvmppc_get_cpu_char()
    - [Config] Add CONFIG_PPC_BARRIER_NOSPEC

* Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log

* autopkgtests run too often, too much and don't skip enough (LP: #1823056)
    - [Debian] Set +x on rebuild testcase.
    - [Debian] Skip rebuild test, for regression-suite deps.
    - [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
    - [Debian] make rebuild use skippable error codes when skipping.
    - [Debian] Only run regression-suite, if requested to.

* bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
    - [Packaging] remove arm64 snapdragon from getabis
    - [Config] config changes for snapdragon split
    - packaging: arm64: disable building the snapdragon flavour
    - [Packaging] arm64: Drop snapdragon from kernel-versions

* CVE-2017-5753
    - KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
    - media: dvb_ca_en50221: prevent using slot_info for Spectre attacs
    - sysvipc/sem: mitigate semnum index against spectre v1
    - libahci: Fix possible Spectre-v1 pmp indexing in ahci_led_store()
    - s390/keyboard: sanitize array index in do_kdsk_ioctl
    - arm64: fix possible spectre-v1 write in ptrace_hbp_set_event()
    - KVM: arm/arm64: vgic: Fix possible spectre-v1 write in vgic_mmio_write_apr()
    - pktcdvd: Fix possible Spectre-v1 for pkt_devs
    - net: socket: fix potential spectre v1 gadget in socketcall
    - net: socket: Fix potential spectre v1 gadget in sock_is_registered
    - drm/amdgpu/pm: Fix potential Spectre v1
    - netlink: Fix spectre v1 gadget in netlink_create()
    - ext4: fix spectre gadget in ext4_mb_regular_allocator()
    - drm/i915/kvmgt: Fix potential Spectre v1
    - net: sock_diag: Fix spectre v1 gadget in __sock_diag_cmd()
    - fs/quota: Fix spectre gadget in do_quotactl
    - hwmon: (nct6775) Fix potential Spectre v1
    - mac80211_hwsim: Fix possible Spectre-v1 for hwsim_world_regdom_custom
    - switchtec: Fix Spectre v1 vulnerability
    - misc: hmc6352: fix potential Spectre v1
    - tty: vt_ioctl: fix potential Spectre v1
    - nl80211: Fix possible Spectre-v1 for NL80211_TXRATE_HT
    - nl80211: Fix possible Spectre-v1 for CQM RSSI thresholds
    - IB/ucm: Fix Spectre v1 vulnerability
    - RDMA/ucma: Fix Spectre v1 vulnerability
    - drm/bufs: Fix Spectre v1 vulnerability
    - usb: gadget: storage: Fix Spectre v1 vulnerability
    - ptp: fix Spectre v1 vulnerability
    - HID: hiddev: fix potential Spectre v1
    - vhost: Fix Spectre V1 vulnerability
    - drivers/misc/sgi-gru: fix Spectre v1 vulnerability
    - ipv4: Fix potential Spectre v1 vulnerability
    - aio: fix spectre gadget in lookup_ioctx
    - ALSA: emux: Fix potential Spectre v1 vulnerabilities
    - ALSA: pcm: Fix potential Spectre v1 vulnerability
    - ip6mr: Fix potential Spectre v1 vulnerability
    - ALSA: rme9652: Fix potential Spectre v1 vulnerability
    - ALSA: emu10k1: Fix potential Spectre v1 vulnerabilities
    - KVM: arm/arm64: vgic: Fix off-by-one bug in vgic_get_irq()
    - drm/ioctl: Fix Spectre v1 vulnerabilities
    - char/mwave: fix potential Spectre v1 vulnerability
    - applicom: Fix potential Spectre v1 vulnerabilities
    - ipmi: msghandler: Fix potential Spectre v1 vulnerabilities
    - powerpc/ptrace: Mitigate potential Spectre v1
    - cfg80211: prevent speculation on cfg80211_classify8021d() return
    - ALSA: rawmidi: Fix potential Spectre v1 vulnerability
    - ALSA: seq: oss: Fix Spectre v1 vulnerability

* Bionic: Sync to Xenial (Spectre) (LP: #1822760)
    - x86/speculation/l1tf: Suggest what to do on systems with too much RAM
    - KVM: SVM: Add MSR-based feature support for serializing LFENCE
    - KVM: VMX: fixes for vmentry_l1d_flush module parameter
    - KVM: X86: Allow userspace to define the microcode version
    - SAUCE: [Fix] x86/KVM/VMX: Add L1D flush logic
    - SAUCE: [Fix] x86/speculation: Use ARCH_CAPABILITIES to skip L1D flush on
      vmentry

* [SRU] [B/OEM] Fix ACPI bug that causes boot failure (LP: #1819921)
    - SAUCE: ACPI / bus: Add some Lenovo laptops in list of acpi table term list

* Bionic update: upstream stable patchset for fuse 2019-04-12 (LP: #1824553)
    - fuse: fix double request_end()
    - fuse: fix unlocked access to processing queue
    - fuse: umount should wait for all requests
    - fuse: Fix oops at process_init_reply()
    - fuse: Don't access pipe->buffers without pipe_lock()
    - fuse: Fix use-after-free in fuse_dev_do_read()
    - fuse: Fix use-after-free in fuse_dev_do_write()
    - fuse: set FR_SENT while locked
    - fuse: fix blocked_waitq wakeup
    - fuse: fix leaked notify reply
    - fuse: fix possibly missed wake-up after abort
    - fuse: fix use-after-free in fuse_direct_IO()
    - fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns ENOSYS
    - fuse: handle zero sized retrieve correctly
    - fuse: call pipe_buf_release() under pipe lock
    - fuse: decrement NR_WRITEBACK_TEMP on the right page

* Backport support for software count cache flush Spectre v2 mitigation. (CVE)
    (required for POWER9 DD2.3) (LP: #1822870) // Backport support for software
    count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)
    (LP: #1822870)
    - powerpc64s: Show ori31 availability in spectre_v1 sysfs file not v2
    - powerpc/fsl: Fix spectre_v2 mitigations reporting
    - powerpc: Avoid code patching freed init sections

* Backport support for software count cache flush Spectre v2 mitigation. (CVE)
    (required for POWER9 DD2.3) (LP: #1822870) // Backport support for software
    count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)
    (LP: #1822870) // Backport support for software count cache flush Spectre v2
    mitigation. (CVE) (required for POWER9 DD2.3) (LP: #1822870)
    - powerpc/security: Fix spectre_v2 reporting

* CVE-2019-3874
    - sctp: use sk_wmem_queued to check for writable space
    - sctp: implement memory accounting on tx path
    - sctp: implement memory accounting on rx path

* NULL pointer dereference when using z3fold and zswap (LP: #1814874)
    - z3fold: fix possible reclaim races

* Kprobe event argument syntax in ftrace from ubuntu_kernel_selftests failed
    on B PowerPC (LP: #1812809)
    - selftests/ftrace: Add ppc support for kprobe args tests

* The Realtek card reader does not enter PCIe 1.1/1.2 (LP: #1825487)
    - misc: rtsx: make various functions static
    - misc: rtsx: Enable OCP for rts522a rts524a rts525a rts5260
    - SAUCE: misc: rtsx: Fixed rts5260 power saving parameter and sd glitch

* headset-mic doesn't work on two Dell laptops. (LP: #1825272)
    - ALSA: hda/realtek - add two more pin configuration sets to quirk table

* CVE-2018-16884
    - sunrpc: use SVC_NET() in svcauth_gss_* functions
    - sunrpc: use-after-free in svc_process_common()

* sky2 ethernet card don't work after returning from suspension (LP: #1798921)
    - sky2: Increase D3 delay again

* CVE-2019-9500
    - brcmfmac: assure SSID length from firmware is limited

* CVE-2019-9503
    - brcmfmac: add subtype check for event handling in data path

* CVE-2019-3882
    - vfio/type1: Limit DMA mappings per container

* Intel I210 Ethernet card not working after hotplug [8086:1533]
    (LP: #1818490)
    - igb: Fix WARN_ONCE on runtime suspend

* bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch
    (LP: #1823972)
    - fuse: fix initial parallel dirops

* amdgpu resume failure: failed to allocate wb slot (LP: #1825074)
    - drm/amdgpu: fix&cleanups for wb_clear

* Pop noise when headset is plugged in or removed from GHS/Line-out jack
    (LP: #1821290)
    - ALSA: hda/realtek - Add unplug function into unplug state of Headset Mode
      for ALC225
    - ALSA: hda/realtek - Disable headset Mic VREF for headset mode of ALC225
    - ALSA: hda/realtek - Add support headset mode for DELL WYSE AIO
    - ALSA: hda/realtek - Add support headset mode for New DELL WYSE NB

* mac80211_hwsim unable to handle kernel NULL pointer dereference
    at0000000000000000  (LP: #1825058)
    - mac80211_hwsim: Timer should be initialized before device registered

* [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04
    upgrade (LP: #1821663)
    - ALSA: hda: Add Intel NUC7i3BNB to the power_save blacklist
    - ALSA: hda - add Lenovo IdeaCentre B550 to the power_save_blacklist
    - ALSA: hda - Add two more machines to the power_save_blacklist

* ubuntu_nbd_smoke_test failed on P9 with Bionic kernel (LP: #1822247)
    - nbd: fix how we set bd_invalidated

* TSC clocksource not available in nested guests (LP: #1822821)
    - kvmclock: fix TSC calibration for nested guests

* 4.15 kernel ip_vs --ops causes performance and hang problem (LP: #1819786)
    - ipvs: fix refcount usage for conns in ops mode

* systemd cause kernel trace "BUG: unable to handle kernel paging request at
    6db23a14" on Cosmic i386 (LP: #1813244) // systemd cause kernel trace "BUG:
    unable to handle kernel paging request at 6db23a14" on Cosmic i386
    (LP: #1813244)
    - openvswitch: fix flow actions reallocation

-- Stefan Bader <stefan.bader@canonical.com>  Mon, 06 May 2019 18:59:24 +0200

Changed in linux (Ubuntu Bionic):
status:	Fix Committed → Fix Released

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-05-14:

#26

Download full text (7.0 KiB)

This bug was fixed in the package linux - 4.18.0-20.21

---------------
linux (4.18.0-20.21) cosmic; urgency=medium

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
    - Documentation/l1tf: Fix small spelling typo
    - x86/cpu: Sanitize FAM6_ATOM naming
    - kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
    - locking/atomics, asm-generic: Move some macros from <linux/bitops.h> to a
      new <linux/bits.h> file
    - tools include: Adopt linux/bits.h
    - x86/msr-index: Cleanup bit defines
    - x86/speculation: Consolidate CPU whitelists
    - x86/speculation/mds: Add basic bug infrastructure for MDS
    - x86/speculation/mds: Add BUG_MSBDS_ONLY
    - x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
    - x86/speculation/mds: Add mds_clear_cpu_buffers()
    - x86/speculation/mds: Clear CPU buffers on exit to user
    - x86/kvm/vmx: Add MDS protection when L1D Flush is not active
    - x86/speculation/mds: Conditionally clear CPU buffers on idle entry
    - x86/speculation/mds: Add mitigation control for MDS
    - x86/speculation/mds: Add sysfs reporting for MDS
    - x86/speculation/mds: Add mitigation mode VMWERV
    - Documentation: Move L1TF to separate directory
    - Documentation: Add MDS vulnerability documentation
    - x86/speculation/mds: Add mds=full,nosmt cmdline option
    - x86/speculation: Move arch_smt_update() call to after mitigation decisions
    - x86/speculation/mds: Add SMT warning message
    - x86/speculation/mds: Fix comment
    - x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
    - x86/speculation/mds: Add 'mitigations=' support for MDS

* CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option

* CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option

  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
    CVE-2018-3646
    - cpu/speculation: Add 'mitigations=' cmdline option
    - x86/speculation: Support 'mitigations=' cmdline option

* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux (4.18.0-19.20) cosmic; urgency=medium

* linux: 4.18.0-19.20 -proposed tracker (LP: #1826171)

* Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
    - [Debian] Set +x on rebuild testcase.
    - [Debian] Skip rebuild test, for regression-suite deps.
    - [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
    - [Debian] make rebuild use skippable error codes when skipping.
    - [Debian] Only run regression-suite, if requested to.

  * CVE-2017-5753
    - s390/keyboard: sanitize array index in do_kdsk_ioctl
    - drm/bufs: Fix Spectre v1 vulnerability
    - drivers/misc/sgi-gru: fix Spectre v1 vulnerability
    - ipv4: Fix potential Spectre v1 vulnerability
    - aio: fix spectre gadget in lookup_ioctx
    - ALSA: emux: Fix potential Spectre v1 vulnerabilities
    - ALSA: pcm: Fix potential Spectre v1 vulnerability
    - ip6mr: Fix potential Spectre v1 vulnerability
    - ALSA: rme9652: Fix potential Spectre v1...

Ubuntu
linux package

NULL pointer dereference when using z3fold and zswap

Bug Description

CVE References

Other bug subscribers

Bug attachments

Remote bug watches

	Status	Importance	Assigned to
Linux	Fix Released	High	linux-kernel-bugs #201603
linux (Ubuntu)	Fix Released	Undecided	Po-Hsu Lin
Bionic	Fix Released	Undecided	Unassigned
Cosmic	Fix Released	Undecided	Unassigned

Ubuntulinux package

NULL pointer dereference when using z3fold and zswap

Bug Description

CVE References

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package