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 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
- net: core: Fix Spectre v1 vulnerability
- phonet: af_phonet: Fix Spectre v1 vulnerability
- nfc: af_nfc: Fix Spectre v1 vulnerability
- can: af_can: Fix Spectre v1 vulnerability
- net: Revert recent Spectre-v1 patches.
- 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
* NULL pointer dereference when using z3fold and zswap (LP: #1814874)
- z3fold: fix possible reclaim races
* The Realtek card reader does not enter PCIe 1.1/1.2 (LP: #1825487)
- 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()
* AMD Rome : Minimal support patches (LP: #1816669)
- x86: irq_remapping: Move irq remapping mode enum
- iommu/amd: Add support for higher 64-bit IOMMU Control Register
- iommu/amd: Add support for IOMMU XT mode
* 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
* CVE-2019-3887
- KVM: x86: nVMX: close leak of L0's x2APIC MSRs (CVE-2019-3887)
- KVM: x86: nVMX: fix x2APIC VTPR read intercept
* 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
* Intel I210 Ethernet card not working after hotplug [8086:1533]
(LP: #1818490)
- igb: Fix WARN_ONCE on runtime suspend
* autofs kernel module missing (LP: #1824333)
- [Config] Update autofs4 path in inclusion list
* tasks doing write()/fsync() hit deadlock in write_cache_pages()
(LP: #1824827)
- mm/page-writeback.c: fix range_cyclic writeback vs writepages deadlock
* 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 Lenovo IdeaCentre B550 to the power_save_blacklist
- ALSA: hda - Add two more machines to the power_save_blacklist
* 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.ba...@canonical.com> Mon, 06 May 2019 18:19:46
+0200
** Changed in: linux (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5715
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5753
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5754
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12126
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12127
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12130
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16884
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3620
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3639
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3646
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3874
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3882
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3887
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9500
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9503
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824827
Title:
tasks doing write()/fsync() hit deadlock in write_cache_pages()
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Disco:
Invalid
Bug description:
[Impact]
* Tasks of a multi-threaded workload doing write() and fsync()
might deadlock in write_cache_pages(), preventing progress.
* The fix addresses a corner case in write_cache_pages() on
the range_cyclic implementation which allows the deadlock.
* Patch:
- commit 64081362e8ff4587b4554087f3cfc73d3e0a4cd7
("mm/page-writeback.c: fix range_cyclic writeback vs
writepages deadlock"), present in v4.20-rc1~92^2~19.
[Test Case]
* This issue originally has been hit by the 'perforce' (p4d)
tool in a XFS filesystem, but it's difficult/rare to occur.
* We've written an userspace + kernel module (kprobes-based)
to reproduce this problem and verify the test kernel/patch.
* The kprobes are strictly tied to particular kernel versions
because of the assembly instruction offsets. We'll provide
updated versions for -updates and -proposed for verification.
* Steps
(see output examples in comments):
- Userspace part:
$ gcc -o test test.c -pthread
- Kernel part:
$ touch Makefile
$ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kprobe-test.o clean
$ make -C /lib/modules/$(uname -r)/build M=$(pwd) obj-m=kprobe-test.o
modules
- Shorter hung task timeout and higher console logging level
to notice the deadlocked tasks sooner, and watch progress:
$ echo 10 | sudo tee /proc/sys/kernel/hung_task_timeout_secs
$ echo 9 | sudo tee /proc/sys/kernel/printk
- Load module / Run userspace part (logging to kernel log) in XFS:
$ sudo insmod kprobe-test.ko
$ cd /path/to/xfs-mountpoint && sudo sh -c 'stdbuf -oL /path/to/test
>/dev/kmsg'
$ sudo rmmod kprobe-test
You may need to ctrl-z with the original kernel as 'test' doesn't
finish.
- Check kernel log or watch the system console:
$ dmesg
Check threads in D state.
$ ps -eLo pid,tid,state,comm | grep D | grep -e test -e kworker
[Regression Potential]
* The patch is small but changes core writeback infrastructure,
so there's a chance this may _affect_ some or other behavior
that has not been validated with our regression testing; not
exactly _break_ it. Please note our regression testing.
* This has been verified with 'xfstests' (not only for XFS fs,
despite its original name), used by major Linux filesystems
for regression testing during development. It's been tested
on systems with 24 and 4 CPUs (to exercise differences in
scalability, parallelism, and workload) and XFS and ext4
(reporter's environment + Ubuntu's default).
No regressions were observed (the set of failed tests is
the same in each system and tests failed in the same way).
* This has also been verified with 'iozone' for write intensive
tests, to exercise the writeback mechanism and no errors were
observed.
* The reporter has been running the test kernel with the patch
for weeks and has not observed any other issues/regressions.
[Other Info]
* This is only required in Cosmic (for the Bionic HWE kernel),
and is already applied in Disco.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824827/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
