| 2019-01-11 13:40:46 |
David Limbeck |
bug |
|
|
added bug |
| 2019-01-11 13:40:46 |
David Limbeck |
attachment added |
|
ipset-nuclear-panic.log https://bugs.launchpad.net/bugs/1811394/+attachment/5228466/+files/ipset-nuclear-panic.log |
|
| 2019-01-11 14:00:06 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-01-11 14:00:07 |
Ubuntu Kernel Bot |
tags |
|
bionic |
|
| 2019-01-31 12:31:45 |
David Limbeck |
tags |
bionic |
apport-collected bionic |
|
| 2019-01-31 12:31:46 |
David Limbeck |
description |
When running the following script: https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear on the 4.15.0-43-generic kernel it leads to a kernel panic.
Tested the same with 17.10 (4.13 kernel) and 18.10 (4.18 kernel) and no problems with those.
The issue was first mentioned in our forum (https://forum.proxmox.com/threads/kernel-panic-ip_set_hash_net.50138/#post-234532) on our own kernel that's based on the Ubuntu 4.15. After further investigations neither Debian 9 (4.9 kernel) nor Arch Linux (4.20 kernel) exhibited that same issue.
The attached log has the errors of one run of the ipset-nuclear script.
The kernel panic on the host side can also be triggered from an unprivileged container (Arch Linux, LXC) |
When running the following script: https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear on the 4.15.0-43-generic kernel it leads to a kernel panic.
Tested the same with 17.10 (4.13 kernel) and 18.10 (4.18 kernel) and no problems with those.
The issue was first mentioned in our forum (https://forum.proxmox.com/threads/kernel-panic-ip_set_hash_net.50138/#post-234532) on our own kernel that's based on the Ubuntu 4.15. After further investigations neither Debian 9 (4.9 kernel) nor Arch Linux (4.20 kernel) exhibited that same issue.
The attached log has the errors of one run of the ipset-nuclear script.
The kernel panic on the host side can also be triggered from an unprivileged container (Arch Linux, LXC)
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 1 Jan 31 12:29 seq
crw-rw----+ 1 root audio 116, 33 Jan 31 12:29 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=3f9884ba-1593-11e9-a795-9abe83d987a0 ro maybe-ubiquity
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-43-generic N/A
linux-backports-modules-4.15.0-43-generic N/A
linux-firmware 1.173.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Uname: Linux 4.15.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lxd plugdev sudo
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.12
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.12
dmi.sys.vendor: QEMU |
|
| 2019-01-31 12:31:47 |
David Limbeck |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234629/+files/CRDA.txt |
|
| 2019-01-31 12:31:49 |
David Limbeck |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234630/+files/CurrentDmesg.txt |
|
| 2019-01-31 12:31:51 |
David Limbeck |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234631/+files/Lspci.txt |
|
| 2019-01-31 12:31:52 |
David Limbeck |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234632/+files/ProcCpuinfo.txt |
|
| 2019-01-31 12:31:53 |
David Limbeck |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234633/+files/ProcCpuinfoMinimal.txt |
|
| 2019-01-31 12:31:53 |
David Limbeck |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234634/+files/ProcEnviron.txt |
|
| 2019-01-31 12:31:55 |
David Limbeck |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234635/+files/ProcInterrupts.txt |
|
| 2019-01-31 12:31:56 |
David Limbeck |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234636/+files/ProcModules.txt |
|
| 2019-01-31 12:31:57 |
David Limbeck |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234637/+files/UdevDb.txt |
|
| 2019-01-31 12:31:58 |
David Limbeck |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1811394/+attachment/5234638/+files/WifiSyslog.txt |
|
| 2019-02-12 13:14:46 |
David Limbeck |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2019-02-21 10:43:24 |
Kai-Heng Feng |
description |
When running the following script: https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear on the 4.15.0-43-generic kernel it leads to a kernel panic.
Tested the same with 17.10 (4.13 kernel) and 18.10 (4.18 kernel) and no problems with those.
The issue was first mentioned in our forum (https://forum.proxmox.com/threads/kernel-panic-ip_set_hash_net.50138/#post-234532) on our own kernel that's based on the Ubuntu 4.15. After further investigations neither Debian 9 (4.9 kernel) nor Arch Linux (4.20 kernel) exhibited that same issue.
The attached log has the errors of one run of the ipset-nuclear script.
The kernel panic on the host side can also be triggered from an unprivileged container (Arch Linux, LXC)
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 1 Jan 31 12:29 seq
crw-rw----+ 1 root audio 116, 33 Jan 31 12:29 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=3f9884ba-1593-11e9-a795-9abe83d987a0 ro maybe-ubiquity
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-43-generic N/A
linux-backports-modules-4.15.0-43-generic N/A
linux-firmware 1.173.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Uname: Linux 4.15.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lxd plugdev sudo
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.12
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.12
dmi.sys.vendor: QEMU |
===SRU Justification===
[Impact]
ipset-nuclear script [1] casues a kernel panic.
[Fix]
"Fix wraparound bug which could lead to memory exhaustion when adding an
x.x.x.x-255.255.255.255 range to any hash:*net* types."
[Test]
User feedbacked this patch solves the issue.
[Regression Potential]
Low. It's also in upstream stable v4.14.
[1] https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear
===Original Bug Report===
When running the following script: https://github.com/DevelopersPL/pkgbuild/blob/master/ipset-nuclear/ipset-nuclear on the 4.15.0-43-generic kernel it leads to a kernel panic.
Tested the same with 17.10 (4.13 kernel) and 18.10 (4.18 kernel) and no problems with those.
The issue was first mentioned in our forum (https://forum.proxmox.com/threads/kernel-panic-ip_set_hash_net.50138/#post-234532) on our own kernel that's based on the Ubuntu 4.15. After further investigations neither Debian 9 (4.9 kernel) nor Arch Linux (4.20 kernel) exhibited that same issue.
The attached log has the errors of one run of the ipset-nuclear script.
The kernel panic on the host side can also be triggered from an unprivileged container (Arch Linux, LXC)
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 1 Jan 31 12:29 seq
crw-rw----+ 1 root audio 116, 33 Jan 31 12:29 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
PciMultimedia:
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=3f9884ba-1593-11e9-a795-9abe83d987a0 ro maybe-ubiquity
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-43-generic N/A
linux-backports-modules-4.15.0-43-generic N/A
linux-firmware 1.173.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Uname: Linux 4.15.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lxd plugdev sudo
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-2.12
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.11.1-0-g0551a4be2c-prebuilt.qemu-project.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.12:cvnQEMU:ct1:cvrpc-i440fx-2.12:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-2.12
dmi.sys.vendor: QEMU |
|
| 2019-02-21 10:43:33 |
Kai-Heng Feng |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-02-21 10:43:33 |
Kai-Heng Feng |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2019-02-22 10:08:55 |
Stefan Bader |
linux (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-02-22 10:09:02 |
Stefan Bader |
linux (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2019-03-04 01:57:49 |
Khaled El Mously |
linux (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2019-03-15 23:37:49 |
Brad Figg |
tags |
apport-collected bionic |
apport-collected bionic verification-needed-bionic |
|
| 2019-03-18 10:36:51 |
Mira Limbeck |
tags |
apport-collected bionic verification-needed-bionic |
apport-collected bionic verification-done-bionic |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2017-5753 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2018-14678 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2018-18021 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2018-19824 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-3459 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-3460 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-6974 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-7221 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-7222 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-7308 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-8912 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-8980 |
|
| 2019-04-02 10:27:35 |
Launchpad Janitor |
cve linked |
|
2019-9213 |
|
| 2019-12-27 03:57:04 |
Po-Hsu Lin |
linux (Ubuntu): status |
Confirmed |
Invalid |
|
