multipath -ll is not showing the disks which are actually multipath

Bug #1718397 reported by bugproxy on 2017-09-20
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu-power-systems project
Critical
Canonical Kernel Team
linux (Ubuntu)
Critical
Ubuntu on IBM Power Systems Bug Triage
Xenial
Critical
Unassigned
Zesty
Critical
Canonical Kernel Team
Artful
Critical
Ubuntu on IBM Power Systems Bug Triage

Bug Description

[Impact]

 * The number of available AIO contexts is severely limited
   on systems with a large number of possible CPUs
   (e.g., IBM POWER8 processors w/ 20ish cores * 8 threads/core,
   and other multithreaded server-class processors).

 * This prevents application such as multipath/directio checker
   to provide all of the available devices to the system.

 * Other applications which depend on AIO can be affected/limited.

 * The patch fixes how aio increments the number of active contexts
   (seen in /proc/sys/fs/aio-nr) and checks that against the global
   limit (seen in /proc/sys/fs/aio-max-nr).

[Test Case]

 * A synthetic test-case is attached (io_setup_v2.c) and demonstrated
   (original/patched kernels) in comment #4.

 * Trying to perform multipath discovery in debug/verbose mode
   (i.e., "multipath -v3" command) with sufficient number of
   individual paths using the "directio" path checker should
   demonstrate the problem/solution as well (i.e., presence or
   not of "io_setup failed" messages).

[Regression Potential]

 * Note the fix is trivial and has been tested by several users,
   even caused the introduction of a new test-case in "libaio";
   (but that can never be a strong enough reason for no more errors).

 * Applications which use aio with small "nr_events" value as argument
   to "io_setup()" now have access to a much larger number of aio contexts;
   but hopefully those apps are already only requesting what they need,
   not trying to get more and more.

 * Applications which relied in the _incorrect_ behavior of '/proc/sys/fs/aio-nr'
   being possibly greater than '/proc/sys/fs/aio-max-nr' might have problems,
   but those apps should be fixed.

Problem Description
=================================
I am facing this issue for Texan Flash storage 840 disks which are coming from coho and salfish adapter

coho adapter with 840 storage is 3G disks and salfish adapter with 840 is 12G disks

I am able to see those disks in lsblk o/p but not in multipath -ll comamnd

0004:01:00.0 Coho: Saturn-X U78C9.001.WZS0060-P1-C6 0x10000090fa2a51f8 host10 Online
0004:01:00.1 Coho: Saturn-X U78C9.001.WZS0060-P1-C6 0x10000090fa2a51f9 host11 Online

0005:09:00.0 Sailfish: QLogic 8GB U78C9.001.WZS0060-P1-C9 0x21000024ff787778 host2 Online
0005:09:00.1 Sailfish: QLogic 8GB U78C9.001.WZS0060-P1-C9 0x21000024ff787779 host4 Online

root@luckyv1:/dev/disk# multipath -ll | grep "size=3.0G" -B 1
root@luckyv1:/dev/disk# multipath -ll | grep "size=12G" -B 1
root@luckyv1:/dev/disk#

== Comment: #3 - Luciano Chavez <email address hidden> - 2016-09-20 20:22:20 ==
I edited /etc/multipath.conf and added
verbosity 6

to crank up the output and ran multipath -ll and saved it off to a text file (attached). All the using the directio checker failed and those using the tur checker seem to work.

Sep 20 20:07:36 | loading //lib/multipath/libcheckdirectio.so checker
Sep 20 20:07:36 | loading //lib/multipath/libprioconst.so prioritizer
Sep 20 20:07:36 | Discover device /sys/devices/pci0000:00/0000:00:00.0/0000:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai
Sep 20 20:07:36 | sdai: udev property ID_WWN whitelisted
Sep 20 20:07:36 | sdai: not found in pathvec
Sep 20 20:07:36 | sdai: mask = 0x25
Sep 20 20:07:36 | sdai: dev_t = 66:32
Sep 20 20:07:36 | open '/sys/devices/pci0000:00/0000:00:00.0/0000:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/block/sdai/size'
Sep 20 20:07:36 | sdai: size = 20971520
Sep 20 20:07:36 | sdai: vendor = IBM
Sep 20 20:07:36 | sdai: product = FlashSystem-9840
Sep 20 20:07:36 | sdai: rev = 1442
Sep 20 20:07:36 | sdai: h:b:t:l = 3:0:0:0
Sep 20 20:07:36 | SCSI target 3:0:0 -> FC rport 3:0-2
Sep 20 20:07:36 | sdai: tgt_node_name = 0x500507605e839800
Sep 20 20:07:36 | open '/sys/devices/pci0000:00/0000:00:00.0/0000:01:00.0/host3/rport-3:0-2/target3:0:0/3:0:0:0/state'
Sep 20 20:07:36 | sdai: path state = running
Sep 20 20:07:36 | sdai: get_state
Sep 20 20:07:36 | sdai: path_checker = directio (internal default)
Sep 20 20:07:36 | sdai: checker timeout = 30 ms (internal default)
Sep 20 20:07:36 | io_setup failed
Sep 20 20:07:36 | sdai: checker init failed

== Comment: #7 - Mauricio Faria De Oliveira <email address hidden> - 2016-09-27 18:32:57 ==
The function is failing at the io_setup() system call.

 @ checkers/directio.c

 int libcheck_init (struct checker * c)
 {
  unsigned long pgsize = getpagesize();
  struct directio_context * ct;
  long flags;

  ct = malloc(sizeof(struct directio_context));
  if (!ct)
          return 1;
  memset(ct, 0, sizeof(struct directio_context));

  if (io_setup(1, &ct->ioctx) != 0) {
          condlog(1, "io_setup failed");
          free(ct);
          return 1;
  }
 <...>

The syscall is failing w/ EAGAIN

 # grep ^io_setup multipath_-v2_-d.strace
 io_setup(1, 0x100163c9130) = -1 EAGAIN (Resource temporarily unavailable)
 io_setup(1, 0x10015bae2c0) = -1 EAGAIN (Resource temporarily unavailable)
 io_setup(1, 0x100164d65a0) = -1 EAGAIN (Resource temporarily unavailable)
 io_setup(1, 0x10016429f20) = -1 EAGAIN (Resource temporarily unavailable)
 io_setup(1, 0x100163535c0) = -1 EAGAIN (Resource temporarily unavailable)
 io_setup(1, 0x10016368510) = -1 EAGAIN (Resource temporarily unavailable)
 <...>

According to the manpage (man 2 io_setup)

 NAME
        io_setup - create an asynchronous I/O context

 DESCRIPTION
        The io_setup() system call creates an asynchronous I/O context suitable for concurrently processing nr_events operations. <...>

 ERRORS
        EAGAIN The specified nr_events exceeds the user's limit of available events, as defined in /proc/sys/fs/aio-max-nr.

On luckyv1:

 root@luckyv1:~/mauricfo/bz146849/sep27# cat /proc/sys/fs/aio-max-nr
 65536

 root@luckyv1:~/mauricfo/bz146849/sep27# cat /proc/sys/fs/aio-nr
 130560

According to linux's Documentation/sysctl/fs.txt [1]

 aio-nr & aio-max-nr:

 aio-nr is the running total of the number of events specified on the
 io_setup system call for all currently active aio contexts. If aio-nr
 reaches aio-max-nr then io_setup will fail with EAGAIN. Note that
 raising aio-max-nr does not result in the pre-allocation or re-sizing
 of any kernel data structures.

Interestingly, aio-nr is greater than aio-max-nr. Hm.

Increased aio-max-nr to 262144, and could get some more maps created.

== Comment: #8 - Mauricio Faria De Oliveira <email address hidden> - 2016-09-27 18:56:08 ==
This attached test-case demonstrates that for each io_setup() request of 1 nr_event, actually 1280 seem to be allocated.

root@luckyv1:~/mauricfo/bz146849/sep27# gcc -o io_setup io_setup.c -laio

root@luckyv1:~/mauricfo/bz146849/sep27# cat /proc/sys/fs/aio-nr
0

root@luckyv1:~/mauricfo/bz146849/sep27# ./io_setup &
[1] 12352
io_setup rc = 0
sleeping 10 seconds...

root@luckyv1:~/mauricfo/bz146849/sep27# cat /proc/sys/fs/aio-nr
1280

<...>
io_destroy rc = 0

[1]+ Done ./io_setup

root@luckyv1:~/mauricfo/bz146849/sep27# cat /proc/sys/fs/aio-nr
0

== Comment: #45 - Mauricio Faria De Oliveira <email address hidden> - 2017-09-19 18:32:10 ==
Verification of this commit with the linux-hwe-edge kernel in -proposed,
using the attached test-case "io_setup_v2.c"

    commit 2a8a98673c13cb2a61a6476153acf8344adfa992
    Author: Mauricio Faria de Oliveira <email address hidden>
    Date: Wed Jul 5 10:53:16 2017 -0300

        fs: aio: fix the increment of aio-nr and counting against aio-max-nr

Test-case (attached)

    $ sudo apt-get install gcc libaio-dev
    $ gcc -o io_setup_v2 io_setup_v2.c -laio

Original kernel:

    - Only 409 io_contexts could be allocated,
    but that took 130880 [ div by 2, per bug] = 65440 slots out of 65535

    $ uname -rv
    4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:18 UTC 2017

    $ ./io_setup_v2 1 65536
    nr_events: 1, nr_requests: 65536
    rc = -11, i = 409
    ^Z
    [1]+ Stopped ./io_setup_v2 1 65536

    $ cat /proc/sys/fs/aio-nr
    130880

    $ cat /proc/sys/fs/aio-max-nr
    65536

    $ kill %%

Patched kernel:

    - Now 65515 io_contexts could be allocated out of 65535 (much better)
      (and reporting correctly, without div by 2.)

    $ uname -rv
    4.11.0-140-generic #20~16.04.1+bz146489 SMP Tue Sep 19 17:46:15 CDT 2017

    $ ./io_setup_v2 1 65536
    nr_events: 1, nr_requests: 65536
    rc = -12, i = 65515
    ^Z
    [1]+ Stopped ./io_setup_v2 1 65536

    $ cat /proc/sys/fs/aio-nr
    65515

    $ kill %%

Default Comment by Bridge

tags: added: architecture-ppc64le bugnameltc-146489 severity-critical targetmilestone-inin16043

Default Comment by Bridge

Default Comment by Bridge

Changed in ubuntu:
assignee: nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
affects: ubuntu → kernel-package (Ubuntu)
Changed in ubuntu-power-systems:
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
importance: Undecided → Critical

Verification of this commit with the linux-hwe-edge kernel in -proposed,
using the attached test-case "io_setup_v2.c"

    commit 2a8a98673c13cb2a61a6476153acf8344adfa992
    Author: Mauricio Faria de Oliveira <email address hidden>
    Date: Wed Jul 5 10:53:16 2017 -0300

        fs: aio: fix the increment of aio-nr and counting against aio-max-nr

Test-case (attached)

    $ sudo apt-get install gcc libaio-dev
    $ gcc -o io_setup_v2 io_setup_v2.c -laio

Original kernel:

    - Only 409 io_contexts could be allocated,
    but that took 130880 [ div by 2, per bug] = 65440 slots out of 65535

    $ uname -rv
    4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:18 UTC 2017

    $ ./io_setup_v2 1 65536
    nr_events: 1, nr_requests: 65536
    rc = -11, i = 409
    ^Z
    [1]+ Stopped ./io_setup_v2 1 65536

    $ cat /proc/sys/fs/aio-nr
    130880

    $ cat /proc/sys/fs/aio-max-nr
    65536

    $ kill %%

Patched kernel:

    - Now 65515 io_contexts could be allocated out of 65535 (much better)
      (and reporting correctly, without div by 2.)

    $ uname -rv
    4.11.0-140-generic #20~16.04.1+bz146489 SMP Tue Sep 19 17:46:15 CDT 2017

    $ ./io_setup_v2 1 65536
    nr_events: 1, nr_requests: 65536
    rc = -12, i = 65515
    ^Z
    [1]+ Stopped ./io_setup_v2 1 65536

    $ cat /proc/sys/fs/aio-nr
    65515

    $ kill %%

description: updated

Added an SRU template to the bug description.

description: updated

Patch posted to the kernel-team mailing list:

[A/Z/X][PATCH] fs: aio: fix the increment of aio-nr and counting against aio-max-nr
https://lists.ubuntu.com/archives/kernel-team/2017-September/087132.html

Changed in kernel-package (Ubuntu):
importance: Undecided → Critical
tags: added: kernel-da-key
affects: kernel-package (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Triaged
Changed in linux (Ubuntu Zesty):
status: New → Triaged
Changed in linux (Ubuntu Xenial):
status: New → Triaged
Changed in linux (Ubuntu Zesty):
importance: Undecided → Critical
Changed in linux (Ubuntu Xenial):
importance: Undecided → Critical
Changed in ubuntu-power-systems:
status: New → Triaged

Default Comment by Bridge

Default Comment by Bridge

Seth Forshee (sforshee) on 2017-09-22
Changed in linux (Ubuntu Artful):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :
Download full text (7.8 KiB)

This bug was fixed in the package linux - 4.13.0-12.13

---------------
linux (4.13.0-12.13) artful; urgency=low

  * linux: 4.13.0-12.13 -proposed tracker (LP: #1718980)

  * [Feature] SKX: Support crystall ridge / far / near memory indication in PEBS
    (LP: #1591813)
    - perf/x86: Move Nehalem PEBS code to flag
    - perf/x86: Fix data source decoding for Skylake

  * Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland
    (LP: #1718679)
    - [Config] CONFIG_DRM_VBOXVIDEO=n

  * ipmmu-vmsa driver breaks arm64 boots (LP: #1718734)
    - [Config] Disable CONFIG_IPMMU_VMSA on arm64

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
    - scsi: cxlflash: Fix vlun resize failure in the shrink path

  * multipath -ll is not showing the disks which are actually multipath
    (LP: #1718397)
    - fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * [Feature] Crystal Ridge - BTT - Rework error clearing (LP: #1704350)
    - libnvdimm, btt: fix a missed NVDIMM_IO_ATOMIC case in the write path
    - libnvdimm, btt: refactor map entry operations with macros
    - libnvdimm, btt: ensure that flags were also unchanged during a map_read
    - libnvdimm, btt: cache sector_size in arena_info
    - libnvdimm: fix potential deadlock while clearing errors
    - libnvdimm, btt: rework error clearing

  * [Feature] Crystal Ridge - have 4k DAX faults use a common zero page
    (LP: #1704439)
    - mm: add vm_insert_mixed_mkwrite()
    - dax: relocate some dax functions
    - dax: use common 4k zero page for dax mmap reads
    - dax: remove DAX code from page_cache_tree_insert()
    - dax: move all DAX radix tree defs to fs/dax.c

  * [bug] 17.10: CDP test fail on platform of Purley-2S/4S/Neoncity,BDW-
    de/ep/ex, (LP: #1716843)
    - SAUCE: (no-up) x86/intel_rdt: Fix cdp info directory files issue

  * [featue] GPIO support for Denverton (LP: #1591829)
    - pinctrl: intel: Add Intel Denverton pin controller support

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
    (LP: #1594214)
    - Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * autopkgtest profile fails to build on armhf (LP: #1717920)
    - [Packaging] autopkgtest -- disable d-i when dropping flavours

  * Artful update to v4.13.3 stable release (LP: #1718412)
    - Revert "net: use lib/percpu_counter API for fragmentation mem accounting"
    - Revert "net: fix percpu memory leaks"
    - gianfar: Fix Tx flow control deactivation
    - vhost_net: correctly check tx avail during rx busy polling
    - ip6_gre: update mtu properly in ip6gre_err
    - udp: drop head states only when all skb references are gone
    - ipv6: fix memory leak with multiple tables during netns destruction
    - ipv6: fix typo in fib6_net_exit()
    - sctp: fix missing wake ups in some situations
    - tcp: fix a request socket leak
    - ip_tunnel: fix setting ttl and tos value in collect_md mode
    - f2fs: let fill_super handle roll-forward errors
    - f2fs: check hot_data for roll-forward recovery
    - x86/fsgsbase/64: Fully initialize FS and GS state in start_thread_common
    - x86/fsgsbase/64: Report FSBASE and GSBA...

Read more...

Changed in linux (Ubuntu Artful):
status: Fix Committed → Fix Released
Changed in ubuntu-power-systems:
status: Triaged → In Progress
Manoj Iyer (manjo) on 2017-10-02
Changed in linux (Ubuntu Zesty):
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
tags: added: triage-a
bugproxy (bugproxy) on 2017-10-09
tags: removed: bugnameltc-146489 kernel-da-key severity-critical triage-a
Changed in linux (Ubuntu Zesty):
status: Triaged → Fix Committed
Changed in linux (Ubuntu Xenial):
status: Triaged → Fix Committed
Changed in ubuntu-power-systems:
status: In Progress → Fix Committed

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 'verification-needed-xenial' to 'verification-failed-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!

tags: added: verification-needed-xenial
tags: added: verification-needed-zesty

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-zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

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!

Hello IBM,

Could you please verify the fix with the xenial and/or zesty kernels currently in -proposed?

Thank you!

Launchpad Janitor (janitor) wrote :
Download full text (4.4 KiB)

This bug was fixed in the package linux - 4.10.0-38.42

---------------
linux (4.10.0-38.42) zesty; urgency=low

  * linux: 4.10.0-38.42 -proposed tracker (LP: #1722330)

  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
    (LP: #1720359)
    - scsi: hpsa: limit transfer length to 1MB

  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
    (LP: #1720977)
    - r8152: fix the list rx_done may be used without initialization

  * Touchpad not detected in Lenovo X1 Yoga / Yoga 720-15IKB (LP: #1700657)
    - mfd: intel-lpss: Add missing PCI ID for Intel Sunrise Point LPSS devices

  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
    - d-i: Add bnxt_en to nic-modules.

  * CVE-2017-1000252
    - KVM: VMX: Do not BUG() on out-of-bounds guest IRQ

  * CVE-2017-10663
    - f2fs: sanity check checkpoint segno and blkoff

  * xfstest sanity checks on seek operations fails (LP: #1696049)
    - xfs: fix off-by-one on max nr_pages in xfs_find_get_desired_pgoff()

  * [P9, Power NV][ WSP][Ubuntu 16.04.03] : perf hw breakpoint command results
    in call traces and system goes for reboot. (LP: #1706033)
    - powerpc/64s: Handle data breakpoints in Radix mode

  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
    5u84 (LP: #1693369)
    - scsi: ses: do not add a device to an enclosure if enclosure_add_links()
      fails.

  * Vlun resize request could fail with cxlflash driver (LP: #1713575)
    - scsi: cxlflash: Fix vlun resize failure in the shrink path

  * More migrations with constant load (LP: #1713576)
    - sched/fair: Prefer sibiling only if local group is under-utilized

  * New PMU fixes for marked events. (LP: #1716491)
    - powerpc/perf: POWER9 PMU stops after idle workaround

  * CVE-2017-14340
    - xfs: XFS_IS_REALTIME_INODE() should be false if no rt device present

  * [Zesty][Yakkety] rtl8192e bug fixes (LP: #1698470)
    - staging: rtl8192e: rtl92e_fill_tx_desc fix write to mapped out memory.
    - staging: rtl8192e: fix 2 byte alignment of register BSSIDR.
    - staging: rtl8192e: rtl92e_get_eeprom_size Fix read size of EPROM_CMD.
    - staging: rtl8192e: GetTs Fix invalid TID 7 warning.

  * Stranded with ENODEV after mdadm --readonly (LP: #1706243)
    - md: MD_CLOSING needs to be cleared after called md_set_readonly or
      do_md_stop

  * multipath -ll is not showing the disks which are actually multipath
    (LP: #1718397)
    - fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * ETPS/2 Elantech Touchpad inconsistently detected (Gigabyte P57W laptop)
    (LP: #1594214)
    - Input: i8042 - add Gigabyte P57 to the keyboard reset table

  * CVE-2017-10911
    - xen-blkback: don't leak stack data via response ring

  * CVE-2017-11176
    - mqueue: fix a use-after-free in sys_mq_notify()

  * implement 'complain mode' in seccomp for developer mode with snaps
    (LP: #1567597)
    - Revert "UBUNTU: SAUCE: seccomp: log actions even when audit is disabled"
    - seccomp: Provide matching filter for introspection
    - seccomp: Sysctl to display available actions
    - seccomp: Operation for checking if an a...

Read more...

Changed in linux (Ubuntu Zesty):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (11.5 KiB)

This bug was fixed in the package linux - 4.4.0-98.121

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

  * linux: 4.4.0-98.121 -proposed tracker (LP: #1722299)

  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
    (LP: #1720359)
    - scsi: hpsa: limit transfer length to 1MB

  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
    (LP: #1720977)
    - r8152: fix the list rx_done may be used without initialization

  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
    - d-i: Add bnxt_en to nic-modules.

  * snapcraft.yaml: add dpkg-dev to the build deps (LP: #1718886)
    - snapcraft.yaml: add dpkg-dev to the build deps

  * Support setting I2C_TIMEOUT via ioctl for i2c-designware (LP: #1718578)
    - i2c: designware: Use transfer timeout from ioctl I2C_TIMEOUT

  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
    5u84 (LP: #1693369)
    - scsi_transport_sas: add function to get SAS endpoint address
    - ses: fix discovery of SATA devices in SAS enclosures
    - scsi: sas: provide stub implementation for scsi_is_sas_rphy
    - scsi: ses: Fix SAS device detection in enclosure

  * multipath -ll is not showing the disks which are actually multipath
    (LP: #1718397)
    - fs: aio: fix the increment of aio-nr and counting against aio-max-nr

  * Support Dell Wireless DW5819/5818 WWAN devices (LP: #1721455)
    - SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819

  * CVE-2017-10911
    - xen-blkback: don't leak stack data via response ring

  * implement 'complain mode' in seccomp for developer mode with snaps
    (LP: #1567597)
    - seccomp: Provide matching filter for introspection
    - seccomp: Sysctl to display available actions
    - seccomp: Operation for checking if an action is available
    - seccomp: Sysctl to configure actions that are allowed to be logged
    - seccomp: Selftest for detection of filter flag support
    - seccomp: Action to log before allowing

  * implement errno action logging in seccomp for strict mode with snaps
    (LP: #1721676)
    - seccomp: Provide matching filter for introspection
    - seccomp: Sysctl to display available actions
    - seccomp: Operation for checking if an action is available
    - seccomp: Sysctl to configure actions that are allowed to be logged
    - seccomp: Selftest for detection of filter flag support
    - seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW

  * [Xenial] update OpenNSL kernel modules to 6.5.10 (LP: #1721511)
    - SAUCE: update OpenNSL kernel modules to 6.5.10

  * Xenial update to 4.4.90 stable release (LP: #1721550)
    - cifs: release auth_key.response for reconnect.
    - mac80211: flush hw_roc_start work before cancelling the ROC
    - KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
    - tracing: Fix trace_pipe behavior for instance traces
    - tracing: Erase irqsoff trace with empty write
    - md/raid5: fix a race condition in stripe batch
    - md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
    - scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
      nlms...

Changed in linux (Ubuntu Xenial):
status: Fix Committed → Fix Released
Changed in ubuntu-power-systems:
status: Fix Committed → Fix Released

Verification done on Xenial v4.4-based kernel.

$ lsb_release -d
Description: Ubuntu 16.04.3 LTS

$ wget 'https://launchpadlibrarian.net/337656213/file_146489.txt' -O io_setup_v2.c
$ sudo apt-get install gcc libaio-dev
$ gcc -o io_setup_v2 io_setup_v2.c -laio

Previous kernel:
---------------

$ sudo apt-get --yes install linux-image-generic=4.4.0.97.102
$ sudo kexec --append="$(cat /proc/cmdline)" --initrd=/boot/initrd.img-4.4.0-97-generic /boot/vmlinux-4.4.0-97-generic
...
$ uname -rv
4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:26:02 UTC 2017

$ ./io_setup_v2 1 65536
nr_events: 1, nr_requests: 65536
rc = -11, i = 409
^Z
[1]+ Stopped ./io_setup_v2 1 65536
$ cat /proc/sys/fs/aio-nr
130880
$ cat /proc/sys/fs/aio-max-nr
65536
$ kill %%

Current kernel:
--------------

$ sudo apt-get --yes install linux-image-generic=4.4.0.98.103
$ sudo kexec --append="$(cat /proc/cmdline)" --initrd=/boot/initrd.img-4.4.0-98-generic /boot/vmlinux-4.4.0-98-generic
...
$ uname -rv
4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 2017

$ ./io_setup_v2 1 65536
nr_events: 1, nr_requests: 65536
rc = -12, i = 65515
^Z
[1]+ Stopped ./io_setup_v2 1 65536

$ cat /proc/sys/fs/aio-nr
65515

$ cat /proc/sys/fs/aio-max-nr
65536

tags: added: verification-done-xenial
removed: verification-needed-xenial

Verification done on Zesty.

$ lsb_release -d
Description: Ubuntu 17.04

$ wget 'https://launchpadlibrarian.net/337656213/file_146489.txt' -O io_setup_v2.c
$ sudo apt-get --yes install gcc libaio-dev
$ gcc -o io_setup_v2 io_setup_v2.c -laio

Previous kernel:
---------------

$ sudo apt-get --yes install linux-image-generic=4.10.0.37.37
$ sudo kexec --append="$(cat /proc/cmdline)" --initrd=/boot/initrd.img-4.10.0-37-generic /boot/vmlinux-4.10.0-37-generic
...
$ uname -rv
4.10.0-37-generic #41-Ubuntu SMP Fri Oct 6 20:22:54 UTC 2017

$ ./io_setup_v2 1 65536
nr_events: 1, nr_requests: 65536
rc = -11, i = 204
^Z
[1]+ Stopped ./io_setup_v2 1 65536

$ cat /proc/sys/fs/aio-nr
130560
$ cat /proc/sys/fs/aio-max-nr
65536
$ kill %%

Current kernel:
--------------

$ sudo apt-get --yes install linux-image-generic=4.10.0.38.38
$ sudo kexec --append="$(cat /proc/cmdline)" --initrd=/boot/initrd.img-4.10.0-38-generic /boot/vmlinux-4.10.0-38-generic
...
$ uname -rv
4.10.0-38-generic #42-Ubuntu SMP Tue Oct 10 13:22:54 UTC 2017
$ ./io_setup_v2 1 65536
nr_events: 1, nr_requests: 65536
rc = -12, i = 65514
^Z
[1]+ Stopped ./io_setup_v2 1 65536
$ cat /proc/sys/fs/aio-nr
65514
$ cat /proc/sys/fs/aio-max-nr
65536
$ kill %%

tags: added: verification-done-zesty
removed: verification-needed-zesty
bugproxy (bugproxy) on 2017-11-27
tags: added: bugnameltc-146489 severity-critical
removed: verification-done-xenial verification-done-zesty
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers