** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications
This bug was fixed in the package linux - 4.13.0-39.44
---
linux (4.13.0-39.44) artful; urgency=medium
* linux: 4.13.0-39.44 -proposed tracker (LP: #1761456)
* intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-
image-4.13.0-37-generic) (LP: #1759920) //
** Changed in: linux (Ubuntu Artful)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications
Fix verified on linux-image-4.13.0-39-generic/artful-proposed.
Thank you for the great work!
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Artful)
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/1734327
Title:
Kernel panic on a nfsroot system
To manage
Since 18.04 seems to give up LSM stacking patchset, safest choice (if
acceptable) would be to completely revert LSM stacking patchset for
17.10 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm wondering if we want to see what type of feedback is first received
from upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage
No plan to land upstream yet. Casey's upstream proposal
(
http://kernsec.org/pipermail/linux-security-module-archive/2017-December/004728.html
) is stalling.
Please carry my patch as UBUNTU: SAUCE: patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That's good news, thanks for testing, Sergey.
Tetsuo, do you know if your patch is going to land upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot
4.13.0-32-generic #35~lp1734327 is not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug go to:
I built a test kernel with the patch from Tetsuo. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1734327
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb
** 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/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2017-December/088715.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To
** Description changed:
+ == SRU Justification ==
+ The following commit introduced a regression identified in bug 1734327:
+ ac8f82a0b6d9 ("UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of
the remaining blobs")
+
+ The regression causes a kernel panic to occur after multiple TCP
4.13.0-17-generic #20~lp1734327JustCommit4ae2508Reverted is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about
I built one more test kernel. This one only has commit 4ae2508
reverted.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1734327/revert-test
Can you test that kernel and report back if it has the bug or not?
--
You received this bug notification because you are
4.13.0-17-generic #20~lp1734327 kernel with commits reverted is not
affected.
Thanks for all your effort.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot
Two commits that stick out in the git log are:
4ae2508 UBUNTU: SAUCE: LSM stacking: add stacking support to apparmor network
hooks
ac8f82a UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of the
remaining blobs
I built a test kernel with these two commits reverted.
The test kernel
4.13.0-13-generic #14~lp1734327Commit8d9d2235a82 is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug
I built the next test kernel, up to the following commit:
8d9d2235a82ea41e65eff607005ea4f334e2e503
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1734327
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
4.13.0-13-generic #14~lp1734327Commit1c8d41925cf is not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this
I started a kernel bisect between 4.13.0-12 and 4.13.0-14. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
1c8d41925cff57972056048511a451040fa3b790
The test kernel can be downloaded from:
Tried 4.13.0-12 from https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/13498518, it's not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic
4.13.0-14 is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug go to:
Can you next try 4.13.0-14:
https://launchpad.net/ubuntu/+source/linux/4.13.0-14.15/+build/13541235
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To
4.13.0-10 is not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug go to:
Thanks again for testing. It's sounding like this was introduced by a
SAUCE patch in the 4.13 kernel. Can you next test the first 4.13 kernel
that came after 4.12.0-13:
4.13.0-10: https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable/+build/13358561
--
You received this bug
Both 4.11.0-5 and 4.12.0-13 are not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug go to:
** Tags removed: needs-bisect
** Tags added: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug
Thanks for testing, Sergey. That further indicates that the regression
is due to a SAUCE patch. We can perform a bisect to identify the exact
commit. We need to narrow down the kernel version that introduced the
bug further. Can you next test the following two kernels:
4.11.0-5:
4.13.0-18 is affected.
4.10.0-41 is not affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug go to:
I wonder if this bug could be caused by a SAUCE patch, which is why it
doesn't happen with the upstream kernels.
Can you see if this bug happens in either the Zesty kernel or Artful
-proposed
Zesty:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/13757667
Artful
4.13-rc1 is not affected either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug go to:
Can you give 4.13-rc1 a try:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage
Unable to reproduce with both 4.13.0 and 4.14-rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734327
Title:
Kernel panic on a nfsroot system
To manage notifications about this bug go to:
I'd like to perform a reverse bisect to figure out which commit upstream
fixes this regression. It would be very helpful to know the last kernel
that had this issue and the first kernel that did not.
Can you test the following kernels and report back? We are looking for
the earliest kernel
Unable to reproduce using upstream kernel 4.14.0-041400-generic.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
apport information
** Tags added: apport-collected
** Description changed:
Summary:
Kernel panic occurs after multiple TCP connection creations/closures to the
localhost.
The bug was found using STAF RPC calls, but is easily reproducible with SSH.
The bug doesn't appear on an identical
40 matches
Mail list logo
