The userspace regression is fixed in latest available kernels for all series:
Xenial (Trusty-HWE): 4.4.0-143
Bionic (Xenial-HWE): 4.15.0-46
Cosmic (Bionic-HWE): 4.18.0-16
Disco (development series): 5.0.0-7.8
Cheers,
Guilherme
--
You received this bug notification because you are a member of U
This bug was fixed in the package linux - 4.19.0-12.13
---
linux (4.19.0-12.13) disco; urgency=medium
* linux: 4.19.0-12.13 -proposed tracker (LP: #1813664)
* kernel oops in bcache module (LP: #1793901)
- SAUCE: bcache: never writeback a discard operation
* Disco update: 4
This bug was fixed in the package linux - 4.4.0-142.168
---
linux (4.4.0-142.168) xenial; urgency=medium
* linux: 4.4.0-142.168 -proposed tracker (LP: #1811846)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* iptables connlimit allows more connectio
This bug was fixed in the package linux - 4.18.0-14.15
---
linux (4.18.0-14.15) cosmic; urgency=medium
* linux: 4.18.0-14.15 -proposed tracker (LP: #1811406)
* CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: Avoid lock contention and thundering he
This bug was fixed in the package linux - 4.4.0-142.168
---
linux (4.4.0-142.168) xenial; urgency=medium
* linux: 4.4.0-142.168 -proposed tracker (LP: #1811846)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* iptables connlimit allows more connectio
There was an userspace regression reported after the inclusion of these
backports;
it's being handled in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873.
The fix patch was released upstream and the SRU request was sent to kernel-team
ML (thanks smb!):
https://lists.ubuntu.com/archi
This bug was fixed in the package linux - 4.15.0-44.47
---
linux (4.15.0-44.47) bionic; urgency=medium
* linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CPU hard lockup with rigorous writes to NVM
I was able to verify/test in both Bionic and Cosmic proposed kernels,
respectively: 4.15.0-44.47 and 4.18.0-14.15.
I don't have a reproducer, but to exercise the paths modified by the
patches, the following approach was taken:
(a) Open ssh connection to the host/test machine, and run the followin
We're still pending the Xenial verification; I'm waiting for the trusty-
HWE kernel to be released in -proposed, since we have a user capable of
reproducing the crash in that version, so I'm planning to ask them to
try in the trusty-HWE package.
--
You received this bug notification because you a
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
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 'verifica
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 'verifica
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
To manage notifications about
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
To manage notifications about this
SRU request was submitted to kernel team.
* For Xenial and trusty-HWE (kernel 4.4):
https://lists.ubuntu.com/archives/kernel-team/2019-January/097556.html
* For Bionic (kernel 4.15) and Cosmic (kernel 4.18):
https://lists.ubuntu.com/archives/kernel-team/2019-January/097562.html
--
You received
** Description changed:
[Impact]
* Line discipline code is racy when we have buffer being flush while the
tty is being initialized or reinitialized. For the first problem, we
have an upstream patch since January 2018: b027e2298bd5 ("tty: fix data
race between tty_init_dev and flush of
** Description changed:
[Impact]
- The following Oops was discovered by user:
+ * Line discipline code is racy when we have buffer being flush while the
+ tty is being initialized or reinitialized. For the first problem, we
+ have an upstream patch since January 2018: b027e2298bd5 ("tty: fix
** Tags removed: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
** Changed in: linux (Ubuntu Xenial)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
To manage notifications about this bug
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => High
--
You re
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
To manage notifications a
** Changed in: linux (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
There's news - a V6 patchset was proposed recently, that address this issue
and there are good chances to get merged:
https://marc.info/?l=linux-kernel&m=154103190111795
("[PATCHv6 0/7] tty: Hold write ldisc sem in tty_reopen()").
Will update here with SRU request when it gets merged.
Cheers,
Quick summary about this issue upstream:
The first thread I found about this dates back to 2016, an user report
followed by some approaches from Peter:
https://lkml.org/lkml/2016/5/16/452
After that, seems the thread died, even with a functional patch, it
wasn't "upstreamed". After about an year,
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Description changed:
[Impact]
The following Oops was discovered by user:
[684766.39] BUG: unable to handle kernel paging request at
2268
[684766.667642] IP: [] n_tty_receive_buf_common+0x6a/0xae0
[684766.668487] PGD 8019574fe067 PUD 19574ff067 PMD 0
[68476
Kernel core dump analysis:
crash> set
PID: 23697
COMMAND: "kworker/u82:0"
TASK: 88370bcfaa80 [THREAD_INFO: 883708104000]
CPU: 33
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 23697 TASK: 88370bcfaa80 CPU: 33 COMMAND: "kworker/u82:0"
[...]
#3 [883708107b78] __bad_area_nosemaphore at 8106a889
** Changed in: linux (Ubuntu)
Milestone: trusty-updates => None
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
The following Oops was discovered by user:
[684766.39] BUG: unable to handle kernel paging reque
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791758
Title:
ldisc crash on reopened tty
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/l
** Attachment added: ""bt" and "bt -l" from Kernel crashdump"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+attachment/5187256/+files/CRASH_BT.log
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a memb
** Attachment added: "Call Trace from dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+attachment/5187255/+files/DMESG_CALL_TRACE.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
32 matches
Mail list logo
