This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
I have tested with 4.4.0-97 and I can't reproduce the above behavior
now.
# uname -r
4.4.0-97-generic
# cat /sys/module/apparmor/parameters/audit
cat: /sys/module/apparmor/parameters/audit: Invalid argument
- Eric
** Tags removed: verification-needed-xenial
** Tags added:
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
For Zesty the change was already applied as "UBUNTU: SAUCE: apparmor: fix
parameters so that the permission test is bypas
sed at boot" (see bug #1678048) in 4.10.0-17.19 (pre release).
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Zesty)
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
A patch[1] has been submitted to Kernel team ML, it is now waiting for
kernel folks ACK and will then fall under the next kernel cycle.
[1] - Email subject :
[PATCH][Xenial][Zesty] UBUNTU: SAUCE: fix oops when disabled and module
parameters, are accessed
--
You received this bug notification
I was also able to reproduce using the above reproducer[1]
[1] - cat /sys/module/apparmor/parameters/audit
I think the problem here is that files in apparmor shouldn't be writable
while apparmor is disable.
-rw---
If I do :
# chmod 400 /sys/module/apparmor/parameters/audit (-r--)
I was also able to reproduce using the above reproducer[1]
[1] - cat /sys/module/apparmor/parameters/audit
I think the problem here is that files in apparmor shouldn't be writable while
apparmor is disable.
(-rw---)
If I do :
# chmod 400 /sys/module/apparmor/parameters/audit (-r)
At first glance, it seems the problem seems to be introduce with
commit[1].
I notice the problem while running the sosreport kernel plugin[2] on a
system with apparmor disable (apparmor=0).
[1] - commit
commit a3c6147c6f4132e943db2cff4e1a85887277fc2a
Author: John Johansen
correct that ubuntu14.04.5 can also reproduce too.
--
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/1626984
Title:
kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
Sorry, I forget to tell that I have disable apparmor through kernel boot
parameter:
GRUB_CMDLINE_LINUX="apparmor=0"
you can try with it.
I will try to get kdump for further checking.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
In testing I have not been able to reproduce.
But from the oops it looks either like potentially like memory corruption, or
corruption of the cred. The oops reports
invalid opcode: [#1] SMP
however the piece of code triggering this is used all the time, so the
more likely scenario is
more information,
1. on ubuntu14.04.4, after this panic reproduced, all the 4.4.x kernel will get
panic when cat /sys/module/apparmor/parameters/audit
2. on ubuntu14.04.5, it is fine with all 4.4.x kernels.
--
You received this bug notification because you are a member of Kernel
Packages,
14 matches
Mail list logo
