[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-08-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 4.4.0-34.53

---
linux (4.4.0-34.53) xenial; urgency=low

  [ Seth Forshee ]

  * Release Tracking Bug
- LP: #1606960

  * [APL][SAUCE] Slow system response time due to a monitor bug (LP: #1606147)
- x86/cpu/intel: Introduce macros for Intel family numbers
- SAUCE: x86/cpu: Add workaround for MONITOR instruction erratum on Goldmont
  based CPUs

linux (4.4.0-33.52) xenial; urgency=low

  [ Seth Forshee ]

  * Release Tracking Bug
- LP: #1605709

  * [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (namespace) Bypass sget() capability check for nfs

linux (4.4.0-32.51) xenial; urgency=low

  [ Seth Forshee ]

  * Release Tracking Bug
- LP: #1604443

  * thinkpad yoga 260 wacom touchscreen not working (LP: #1603975)
- HID: wacom: break out parsing of device and registering of input
- HID: wacom: Initialize hid_data.inputmode to -1
- HID: wacom: Support switching from vendor-defined device mode on G9 and 
G11

  * changelog: add CVEs as first class citizens (LP: #1604344)
- use CVE numbers in changelog

  * [Xenial] Include Huawei PCIe SSD hio kernel driver (LP: #1603483)
- SAUCE: import Huawei ES3000_V2 (2.1.0.23)
- SAUCE: hio: bio_endio() no longer takes errors arg
- SAUCE: hio: blk_queue make_request_fn now returns a blk_qc_t
- SAUCE: hio: use alloc_cpumask_var to avoid -Wframe-larger-than
- SAUCE: hio: fix mask maybe-uninitialized warning
- [config] enable CONFIG_HIO (Huawei ES3000_V2 PCIe SSD driver)
- SAUCE: hio: Makefile and Kconfig

  * CVE-2016-5243 (LP: #1589036)
- tipc: fix an infoleak in tipc_nl_compat_link_dump
- tipc: fix nl compat regression for link statistics

  * CVE-2016-4470
- KEYS: potential uninitialized variable

  * integer overflow in xt_alloc_table_info (LP: #1555353)
- netfilter: x_tables: check for size overflow

  * CVE-2016-3135:
- Revert "UBUNTU: SAUCE: (noup) netfilter: x_tables: check for size 
overflow"

  * CVE-2016-4440 (LP: #1584192)
- kvm:vmx: more complete state update on APICv on/off

  * the system hangs in the dma driver when reboot or shutdown on a baytrail-m
laptop (LP: #1602579)
- dmaengine: dw: platform: power on device on shutdown
- ACPI / LPSS: override power state for LPSS DMA device

  * Add proper  palm detection support for MS Precision Touchpad (LP: #1593124)
- Revert "HID: multitouch: enable palm rejection if device implements
  confidence usage"
- HID: multitouch: enable palm rejection for Windows Precision Touchpad

  * Add support for Intel 8265 Bluetooth ([8087:0A2B]) (LP: #1599068)
- Bluetooth: Add support for Intel Bluetooth device 8265 [8087:0a2b]

  * CVE-2016-4794 (LP: #1581871)
- percpu: fix synchronization between chunk->map_extend_work and chunk
  destruction
- percpu: fix synchronization between synchronous map extension and chunk
  destruction

  * Xenial update to v4.4.15 stable release (LP: #1601952)
- net_sched: fix pfifo_head_drop behavior vs backlog
- net: Don't forget pr_fmt on net_dbg_ratelimited for CONFIG_DYNAMIC_DEBUG
- sit: correct IP protocol used in ipip6_err
- esp: Fix ESN generation under UDP encapsulation
- netem: fix a use after free
- ipmr/ip6mr: Initialize the last assert time of mfc entries.
- Bridge: Fix ipv6 mc snooping if bridge has no ipv6 address
- sock_diag: do not broadcast raw socket destruction
- bpf, perf: delay release of BPF prog after grace period
- neigh: Explicitly declare RCU-bh read side critical section in 
neigh_xmit()
- net: macb: fix default configuration for GMAC on AT91
- net: alx: Work around the DMA RX overflow issue
- bpf: try harder on clones when writing into skb
- AX.25: Close socket connection on session completion
- crypto: ux500 - memmove the right size
- crypto: user - re-add size check for CRYPTO_MSG_GETALG
- USB: uas: Fix slave queue_depth not being set
- usb: quirks: Fix sorting
- usb: quirks: Add no-lpm quirk for Acer C120 LED Projector
- usb: musb: only restore devctl when session was set in backup
- usb: musb: Stop bulk endpoint while queue is rotated
- usb: musb: Ensure rx reinit occurs for shared_fifo endpoints
- usb: musb: host: correct cppi dma channel for isoch transfer
- usb: xhci-plat: properly handle probe deferral for devm_clk_get()
- USB: xhci: Add broken streams quirk for Frescologic device id 1009
- xhci: Fix handling timeouted commands on hosts in weird states.
- USB: mos7720: delete parport
- usb: gadget: fix spinlock dead lock in gadgetfs
- usb: host: ehci-tegra: Grab the correct UTMI pads reset
- usb: dwc3: exynos: Fix deferred probing storm.
- Linux 4.4.15

  * qeth: delete napi struct when removing a qeth device (LP: #1601831)
- qeth: delete napi struct when removing a qeth device

  *

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-08-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 3.19.0-66.74

---
linux (3.19.0-66.74) vivid; urgency=low

  [ Seth Forshee ]

  * Release Tracking Bug
- LP: #1604153

  * CVE-2016-1237
- posix_acl: Add set_posix_acl
- nfsd: check permissions when setting ACLs

  * changelog: add CVEs as first class citizens (LP: #1604344)
- use CVE numbers in changelog

  * CVE-2016-5243 (LP: #1589036)
- tipc: fix an infoleak in tipc_nl_compat_link_dump

  * CVE-2016-4470
- KEYS: potential uninitialized variable

  * CVE-2016-4794 (LP: #1581871)
- percpu: fix synchronization between chunk->map_extend_work and chunk
  destruction
- percpu: fix synchronization between synchronous map extension and chunk
  destruction

  * qeth: delete napi struct when removing a qeth device (LP: #1601831)
- qeth: delete napi struct when removing a qeth device

  * arm64: statically link rtc-efi (LP: #1583738)
- [Config] Link rtc-efi statically on arm64

  * linux: Homogenize changelog format across releases (LP: #1599562)
- Revert "UBUNTU: [debian] BugLink: close LP: bugs only for Launchpad urls"
- [Debian] git-ubuntu-log -- switch to bug order
- [Debian] git-ubuntu-log -- fix empty section formatting
- [Debian] git-ubuntu-log -- output should be utf-8
- [Debian] git-ubuntu-log -- handle invalid or private bugs
- [Debian] git-ubuntu-log -- wrap long bug and commit titles
- [Debian] git-ubuntu-log -- ensure we get the last commit
- [Debian] git-ubuntu-log -- prevent bug references being split
- [Debian] git-ubuntu-log -- git log output is UTF-8

  * exercising ptys causes a kernel oops (LP: #1586418)
- devpts: fix null pointer dereference on failed memory allocation

  * the kernel hangs when reboot or shutdown on a lenovo baytrail-m based
machine (LP: #1597564)
- usb: xhci: Makefile: move xhci-pci and xhci-plat-hcd after xhci-hcd

  * [i915_bpo][SKL] Display core init/uninit updates (LP: #1595803)
- SAUCE: i915_bpo: drm/i915: Extract a intel_power_well_enable() function
- SAUCE: i915_bpo: drm/i915: Extract a intel_power_well_disable() function
- SAUCE: i915_bpo: drm/i915/skl: Making DC6 entry is the last call in 
suspend
  flow.
- SAUCE: i915_bpo: drm/i915: Kill intel_runtime_pm_disable()
- SAUCE: i915_bpo: drm/i915/gen9: csr_init after runtime pm enable
- SAUCE: i915_bpo: drm/i915: use correct power domain for csr loading
- SAUCE: i915_bpo: drm/i915/gen9: Don't try to load garbage dmc firmware on
  resume
- SAUCE: i915_bpo: drm/i915/skl: Removed assert for csr-fw-loading check
  during disabling dc6
- SAUCE: i915_bpo: drm/i915: fix the power well ID for always on wells
- SAUCE: i915_bpo: drm/i915: fix lookup_power_well for power wells without 
any
  domain
- SAUCE: i915_bpo: drm/i915: Make turning on/off PW1 and Misc I/O part of 
the
  init/fini sequences

 -- Seth Forshee   Tue, 19 Jul 2016 09:07:26
-0500

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-08-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 3.13.0-93.140

---
linux (3.13.0-93.140) trusty; urgency=low

  [ Seth Forshee ]

  * Release Tracking Bug
- LP: #1604134

  * Boot failure with EFI stub (LP: #1603476)
- x86/efi: Fix boot failure with EFI stub

  * CVE-2016-5243 (LP: #1589036)
- tipc: fix an infoleak in tipc_nl_compat_link_dump

  * qeth: delete napi struct when removing a qeth device (LP: #1601831)
- qeth: delete napi struct when removing a qeth device

  * deadlock on balloon deflation (LP: #1598197)
- SAUCE: mm/balloon_compaction: Fix Regression of LP#1572562

  * serial: 8250_pci: Add support for 16 port Exar boards (LP: #1447485)
- serial: 8250_pci: Add support for 16 port Exar boards
- serial: 8250_pci: Add support for 12 port Exar boards
- serial: 8250_pci: Correct uartclk for xr17v35x expansion chips

  * linux: Homogenize changelog format across releases (LP: #1599562)
- Revert "UBUNTU: [debian] BugLink: close LP: bugs only for Launchpad urls"
- [Debian] git-ubuntu-log -- switch to bug order
- [Debian] git-ubuntu-log -- fix empty section formatting
- [Debian] git-ubuntu-log -- output should be utf-8
- [Debian] git-ubuntu-log -- handle invalid or private bugs
- [Debian] git-ubuntu-log -- wrap long bug and commit titles
- [Debian] git-ubuntu-log -- ensure we get the last commit
- [Debian] git-ubuntu-log -- prevent bug references being split
- [Debian] git-ubuntu-log -- git log output is UTF-8

  * exercising ptys causes a kernel oops (LP: #1586418)
- devpts: fix null pointer dereference on failed memory allocation

  * Miscellaneous upstream changes
- KEYS: potential uninitialized variable

 -- Seth Forshee   Mon, 18 Jul 2016 15:05:56
-0500

** Changed in: linux (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-1237

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  []

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-08-02 Thread Colin Ian King 
Even though I'm on vacation I still managed to squeeze in some time to
test this on trusty before the 5 days deadline ran out.  I have
exercised the kernel with a 20 minutes soak test and was unable to trip
the bug with the trusty -proposed kernel.  Without the fix, the issue
can be triggered, with the fix, I can't trigger the issue.

Marking it as verification-done-trusty

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-08-02 Thread Seth Forshee 
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-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-28 Thread Colin Ian King 
I've exhaustively exercised this and cannot reproduce the issue with the
-proposed 3.19.0-66-generic #74 kernel. Marking it as verification-done

** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB 
inactive_file:47608kB unevictable:3164kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:872588kB mlocked:3164kB dirty:180kB writeback:0kB 
mapped:16216kB shmem:3620kB slab_reclaimable:18304kB slab_unreclaimable:23380kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-28 Thread Colin Ian King 
I've exhaustively exercised this and cannot reproduce the issue with the
-proposed 4.4.0-34-generic #53 kernel. Marking it as verification-done

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB 
inactive_file:47608kB unevictable:3164kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:872588kB mlocked:3164kB dirty:180kB writeback:0kB 
mapped:16216kB shmem:3620kB slab_reclaimable:18304kB slab_unreclaimable:23380kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-28 Thread Colin Ian King 
** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB 
inactive_file:47608kB unevictable:3164kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:872588kB mlocked:3164kB dirty:180kB writeback:0kB 
mapped:16216kB shmem:3620kB slab_reclaimable:18304kB slab_unreclaimable:23380kB 
kernel_stack:1568kB pagetables:688kB unstable:0kB bounce:0kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-28 Thread Seth Forshee 
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 verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-28 Thread Seth Forshee 
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-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

** Tags added: verification-needed-xenial

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-25 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 4.4.0-33.52

---
linux (4.4.0-33.52) xenial; urgency=low

  [ Seth Forshee ]

  * Release Tracking Bug
- LP: #1605709

  * [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE: (namespace) Bypass sget() capability check for nfs

linux (4.4.0-32.51) xenial; urgency=low

  [ Seth Forshee ]

  * Release Tracking Bug
- LP: #1604443

  * thinkpad yoga 260 wacom touchscreen not working (LP: #1603975)
- HID: wacom: break out parsing of device and registering of input
- HID: wacom: Initialize hid_data.inputmode to -1
- HID: wacom: Support switching from vendor-defined device mode on G9 and 
G11

  * changelog: add CVEs as first class citizens (LP: #1604344)
- use CVE numbers in changelog

  * [Xenial] Include Huawei PCIe SSD hio kernel driver (LP: #1603483)
- SAUCE: import Huawei ES3000_V2 (2.1.0.23)
- SAUCE: hio: bio_endio() no longer takes errors arg
- SAUCE: hio: blk_queue make_request_fn now returns a blk_qc_t
- SAUCE: hio: use alloc_cpumask_var to avoid -Wframe-larger-than
- SAUCE: hio: fix mask maybe-uninitialized warning
- [config] enable CONFIG_HIO (Huawei ES3000_V2 PCIe SSD driver)
- SAUCE: hio: Makefile and Kconfig

  * CVE-2016-5243 (LP: #1589036)
- tipc: fix an infoleak in tipc_nl_compat_link_dump
- tipc: fix nl compat regression for link statistics

  * CVE-2016-4470
- KEYS: potential uninitialized variable

  * integer overflow in xt_alloc_table_info (LP: #1555353)
- netfilter: x_tables: check for size overflow

  * CVE-2016-3135:
- Revert "UBUNTU: SAUCE: (noup) netfilter: x_tables: check for size 
overflow"

  * CVE-2016-4440 (LP: #1584192)
- kvm:vmx: more complete state update on APICv on/off

  * the system hangs in the dma driver when reboot or shutdown on a baytrail-m
laptop (LP: #1602579)
- dmaengine: dw: platform: power on device on shutdown
- ACPI / LPSS: override power state for LPSS DMA device

  * Add proper  palm detection support for MS Precision Touchpad (LP: #1593124)
- Revert "HID: multitouch: enable palm rejection if device implements
  confidence usage"
- HID: multitouch: enable palm rejection for Windows Precision Touchpad

  * Add support for Intel 8265 Bluetooth ([8087:0A2B]) (LP: #1599068)
- Bluetooth: Add support for Intel Bluetooth device 8265 [8087:0a2b]

  * CVE-2016-4794 (LP: #1581871)
- percpu: fix synchronization between chunk->map_extend_work and chunk
  destruction
- percpu: fix synchronization between synchronous map extension and chunk
  destruction

  * Xenial update to v4.4.15 stable release (LP: #1601952)
- net_sched: fix pfifo_head_drop behavior vs backlog
- net: Don't forget pr_fmt on net_dbg_ratelimited for CONFIG_DYNAMIC_DEBUG
- sit: correct IP protocol used in ipip6_err
- esp: Fix ESN generation under UDP encapsulation
- netem: fix a use after free
- ipmr/ip6mr: Initialize the last assert time of mfc entries.
- Bridge: Fix ipv6 mc snooping if bridge has no ipv6 address
- sock_diag: do not broadcast raw socket destruction
- bpf, perf: delay release of BPF prog after grace period
- neigh: Explicitly declare RCU-bh read side critical section in 
neigh_xmit()
- net: macb: fix default configuration for GMAC on AT91
- net: alx: Work around the DMA RX overflow issue
- bpf: try harder on clones when writing into skb
- AX.25: Close socket connection on session completion
- crypto: ux500 - memmove the right size
- crypto: user - re-add size check for CRYPTO_MSG_GETALG
- USB: uas: Fix slave queue_depth not being set
- usb: quirks: Fix sorting
- usb: quirks: Add no-lpm quirk for Acer C120 LED Projector
- usb: musb: only restore devctl when session was set in backup
- usb: musb: Stop bulk endpoint while queue is rotated
- usb: musb: Ensure rx reinit occurs for shared_fifo endpoints
- usb: musb: host: correct cppi dma channel for isoch transfer
- usb: xhci-plat: properly handle probe deferral for devm_clk_get()
- USB: xhci: Add broken streams quirk for Frescologic device id 1009
- xhci: Fix handling timeouted commands on hosts in weird states.
- USB: mos7720: delete parport
- usb: gadget: fix spinlock dead lock in gadgetfs
- usb: host: ehci-tegra: Grab the correct UTMI pads reset
- usb: dwc3: exynos: Fix deferred probing storm.
- Linux 4.4.15

  * qeth: delete napi struct when removing a qeth device (LP: #1601831)
- qeth: delete napi struct when removing a qeth device

  * Adjust KBL PCI-ID's (LP: #1600124)
- drm/i915: Add more Kabylake PCI IDs.
- drm/i915: Removing PCI IDs that are no longer listed as Kabylake.

  * [i915_bpo] Rebase driver to v4.7-rc6 + gen9 workarounds + KBP PCH support
(LP: #1599109)
- drm/kms_helper: Add a common place to call init and exit functions.
- drm: Add helper for

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-11 Thread Kamal Mostafa 
No further updates are planned for Wily's kernel.

** Changed in: linux (Ubuntu Wily)
   Status: Fix Committed => Won't Fix

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Won't Fix
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB 
inactive_file:47608kB unevictable:3164kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:872588kB mlocked:3164kB dirty:180kB writeback:0kB 
mapped:16216kB shmem:3620kB slab_reclaimable:18304kB slab_unreclaimable:23380kB 
kernel_stack:1568kB pagetables:688kB unstable:0kB bounce:0kB free_pcp:3736kB 
local_pcp:224kB free_cma:0kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-06 Thread Kamal Mostafa 
** Changed in: linux (Ubuntu Trusty)
   Status: New => Fix Committed

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB 
inactive_file:47608kB unevictable:3164kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:872588kB mlocked:3164kB dirty:180kB writeback:0kB 
mapped:16216kB shmem:3620kB slab_reclaimable:18304kB slab_unreclaimable:23380kB 
kernel_stack:1568kB pagetables:688kB unstable:0kB bounce:0kB free_pcp:3736kB 
local_pcp:224kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable?

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-06 Thread Kamal Mostafa 
** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Wily)
   Status: New => Fix Committed

** Changed in: linux (Ubuntu Vivid)
   Status: New => Fix Committed

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB 
inactive_file:47608kB unevictable:3164kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:872588kB mlocked:3164kB dirty:180kB writeback:0kB 
mapped:16216kB shmem:3620kB slab_reclaimable:18304kB slab_unreclaimable:23380kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-06 Thread Kamal Mostafa 
** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Committed

-- 
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/1586418

Title:
  exercising ptys causes a kernel oops

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  New
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]

  Running stress-ng --pty 1 with a very low vmalloc memory available can
  trip an oops.  This can be generally only be reproduced when memory is
  under a high amount of pressure.  I was able to reproduce reliably by
  forcefully injecting vmalloc to return NULL when the stress-ng pty was
  running.

  [FIX]
  Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.

  [TEST]
  Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.

  --

  running: "stress-ng --pty 1" and this occurs in less than 1 second:

  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB

[Kernel-packages] [Bug 1586418] Re: exercising ptys causes a kernel oops

2016-07-05 Thread Colin Ian King 
** Description changed:

+ [SRU JUSTIFICATION][TRUSTY][WILY][XENIAL]
+ 
+ Running stress-ng --pty 1 with a very low vmalloc memory available can
+ trip an oops.  This can be generally only be reproduced when memory is
+ under a high amount of pressure.  I was able to reproduce reliably by
+ forcefully injecting vmalloc to return NULL when the stress-ng pty was
+ running.
+ 
+ [FIX]
+ Upstream commit 5353ed8deedee9e5acb9f896e9032158f5d998de ("devpts: fix null 
pointer dereference on failed memory allocation"). This needs backporting to 
Yakkey, Xenial, Wily and Trusty because of changes in variable names.
+ 
+ [TEST]
+ Forcefully inject vmalloc to return NULL when running the pty stressor. 
Without the fix, an oops can be tripped, with the fix, no issues occur.
+ 
+ --
+ 
  running: "stress-ng --pty 1" and this occurs in less than 1 second:
  
  [   67.753230] alloc_vmap_area: 9 callbacks suppressed
  [   67.753233] vmap allocation for size 16384 failed: use vmalloc= to 
increase size.
  [   67.753235] vmalloc: allocation failure: 8844 bytes
  [   67.753237] stress-ng-pty: page allocation failure: order:0, mode:0x24000c2
  [   67.753240] CPU: 2 PID: 2150 Comm: stress-ng-pty Not tainted 
4.4.0-23-generic #41-Ubuntu
  [   67.753241] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [   67.753243]  c1abf967 0832d3cc 0286 f2497c8c c139fe1f c19ce22c 
0001 f2497cbc
  [   67.753248]  c1177396 c19cc624 f506b5f0  024000c2 f2497cd0 
c19ce22c f2497ca4
  [   67.753252]  0832d3cc 228c  f2497cec c11ad2ff 024000c2 
 c19ce22c
  [   67.753256] Call Trace:
  [   67.753264]  [] dump_stack+0x58/0x79
  [   67.753267]  [] warn_alloc_failed+0xd6/0x110
  [   67.753272]  [] __vmalloc_node_range+0x1ef/0x210
  [   67.753276]  [] ? tty_get_pgrp+0x40/0x40
  [   67.753278]  [] __vmalloc_node+0x66/0x70
  [   67.753280]  [] ? n_tty_open+0x16/0xc0
  [   67.753283]  [] vmalloc+0x38/0x40
  [   67.753284]  [] ? n_tty_open+0x16/0xc0
  [   67.753290]  [] n_tty_open+0x16/0xc0
  [   67.753293]  [] tty_ldisc_open.isra.2+0x28/0x60
  [   67.753295]  [] tty_ldisc_setup+0x1c/0x70
  [   67.753297]  [] tty_init_dev+0x7c/0x180
  [   67.753301]  [] ? devpts_new_index+0xf1/0x120
  [   67.753303]  [] ptmx_open+0x75/0x160
  [   67.753306]  [] chrdev_open+0xa4/0x180
  [   67.753310]  [] do_dentry_open+0x1ec/0x300
  [   67.753312]  [] ? cdev_put+0x20/0x20
  [   67.753314]  [] vfs_open+0x4f/0x60
  [   67.753316]  [] path_openat+0x509/0x1140
  [   67.753318]  [] ? putname+0x54/0x60
  [   67.753321]  [] do_filp_open+0x68/0xe0
  [   67.753324]  [] ? __alloc_fd+0x36/0x150
  [   67.753326]  [] do_sys_open+0x128/0x2b0
  [   67.753329]  [] SyS_open+0x22/0x30
  [   67.753332]  [] do_fast_syscall_32+0x8d/0x150
  [   67.753336]  [] sysenter_past_esp+0x3d/0x61
  [   67.753338] Mem-Info:
  [   67.753342] active_anon:5790 inactive_anon:1203 isolated_anon:0
  active_file:30258 inactive_file:14843 isolated_file:0
  unevictable:856 dirty:46 writeback:0 unstable:0
  slab_reclaimable:4643 slab_unreclaimable:5952
  mapped:5271 shmem:1380 pagetables:193 bounce:0
  free:166082 free_pcp:1176 free_cma:0
  [   67.753349] DMA free:9616kB min:788kB low:984kB high:1180kB 
active_anon:288kB inactive_anon:112kB active_file:2436kB inactive_file:1216kB 
unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB 
managed:15916kB mlocked:0kB dirty:4kB writeback:0kB mapped:396kB shmem:108kB 
slab_reclaimable:268kB slab_unreclaimable:428kB kernel_stack:24kB 
pagetables:8kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB 
writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
  [   67.753350] lowmem_reserve[]: 0 818 949 949
  [   67.753357] Normal free:567248kB min:41608kB low:52008kB high:62412kB 
active_anon:18440kB inactive_anon:2992kB active_file:101312kB 
inactive_file:47608kB unevictable:3164kB isolated(anon):0kB isolated(file):0kB 
present:897016kB managed:872588kB mlocked:3164kB dirty:180kB writeback:0kB 
mapped:16216kB shmem:3620kB slab_reclaimable:18304kB slab_unreclaimable:23380kB 
kernel_stack:1568kB pagetables:688kB unstable:0kB bounce:0kB free_pcp:3736kB 
local_pcp:224kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable? no
  [   67.753358] lowmem_reserve[]: 0 0 1055 1055
  [   67.753364] HighMem free:87464kB min:128kB low:1804kB high:3480kB 
active_anon:4432kB inactive_anon:1708kB active_file:17284kB 
inactive_file:10548kB unevictable:260kB isolated(anon):0kB isolated(file):0kB 
present:135044kB managed:135044kB mlocked:260kB dirty:0kB writeback:0kB 
mapped:4472kB shmem:1792kB slab_reclaimable:0kB slab_unreclaimable:0kB 
kernel_stack:0kB pagetables:76kB unstable:0kB bounce:0kB free_pcp:968kB 
local_pcp:152kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable? no
  [   67.753365] lowmem_reserve[]: 0 0