[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Launchpad Bug Tracker]

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

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

  [ Andy Whitcroft ]

  * Release Tracking Bug
- LP: #1539090
  * SAUCE: hv: hv_set_ifconfig -- convert to python3
- LP: #1506521
  * SAUCE: dm: introduce a target_ioctl op to allow target specific ioctls
- LP: #1538618

  [ Colin Ian King ]

  * SAUCE: ACPI / tables: Add acpi_force_32bit_fadt_addr option to force 32
bit FADT addresses (LP: #1529381)
- LP: #1529381

  [ John Johansen ]

  * SAUCE: (no-up): apparmor: fix for failed mediation of socket that is
being shutdown
- LP: #1446906

  [ Mahesh Salgaonkar ]

  * SAUCE: Powernv: Remove the usage of PACAR1 from opal wrappers
- LP: #1537881
  * SAUCE: powerpc/book3s: Fix TB corruption in guest exit path on HMI
interrupt.
- LP: #1537881
  * SAUCE: KVM: PPC: Book3S HV: Fix soft lockups in KVM on HMI for time
base errors
- LP: #1537881

  [ Paolo Pisati ]

  * SAUCE: arm64: errata: Add -mpc-relative-literal-loads to erratum
#843419 build flags
- LP: #1533009
  * [Config] MFD_TPS65217=y && REGULATOR_TPS65217=y
  * [Config] disable ARCH_ZX (ZTE ZX Soc)

  [ Tim Gardner ]

  * Revert "SAUCE: (noup) cxlflash: a couple off by one bugs"
  * SAUCE: (no-up) Update bnx2x firmware to 7.12.30.0
- LP: #1536719
  * SAUCE: drop obsolete bnx2x firmware
  * SAUCE: i40e: Silence 'may be used uninitialized' warnings
- LP: #1536474
  * [Config] CONFIG_ZONE_DMA=y for amd64 lowlatency
- LP: #1534647
  * [Config] Add pvpanic to virtual flavour
- LP: #1537923
  * [Config] CONFIG_INTEL_PUNIT_IPC=m, CONFIG_INTEL_TELEMETRY=m
- LP: #1520457

  [ Upstream Kernel Changes ]

  * i40evf: fix compiler warning of unused variable
- LP: #1536474
  * intel: i40e: fix confused code
- LP: #1536474
  * i40e/i40evf: remove unused tunnel parameter
- LP: #1536474
  * i40e: Change BUG_ON to WARN_ON in service event complete
- LP: #1536474
  * i40e: remove BUG_ON from feature string building
- LP: #1536474
  * i40e: remove BUG_ON from FCoE setup
- LP: #1536474
  * i40e: Workaround fix for mss < 256 issue
- LP: #1536474
  * i40e/i40evf: Add a stat to track how many times we have to do a force
WB
- LP: #1536474
  * i40e: Move the saving of old link info from handle_link_event to
link_event
- LP: #1536474
  * i40e/i40evf: Add comment to #endif
- LP: #1536474
  * i40e/i40evf: clean up error messages
- LP: #1536474
  * i40evf: handle many MAC filters correctly
- LP: #1536474
  * i40e: return the number of enabled queues for ETHTOOL_GRXRINGS
- LP: #1536474
  * i40e: rework the functions to configure RSS with similar parameters
- LP: #1536474
  * i40e: create a generic configure rss function
- LP: #1536474
  * i40e: Bump version to 1.4.2
- LP: #1536474
  * i40e: add new fields to store user configuration
- LP: #1536474
  * i40e: rename rss_size to alloc_rss_size in i40e_pf
- LP: #1536474
  * i40e/i40evf: Fix RS bit update in Tx path and disable force WB
workaround
- LP: #1536474
  * i40e/i40evf: prefetch skb data on transmit
- LP: #1536474
  * i40evf: rename VF adapter specific RSS function
- LP: #1536474
  * i40evf: create a generic config RSS function
- LP: #1536474
  * i40evf: create a generic get RSS function
- LP: #1536474
  * i40evf: add new fields to store user configuration of RSS
- LP: #1536474
  * i40e: Update error messaging
- LP: #1536474
  * i40e: fix confusing message
- LP: #1536474
  * i40e: make error message more useful
- LP: #1536474
  * i40evf: quoth the VF driver, Nevermore
- LP: #1536474
  * i40evf: allocate queue vectors dynamically
- LP: #1536474
  * i40evf: allocate ring structs dynamically
- LP: #1536474
  * i40e/i40evf: Bump i40e version to 1.4.4 and i40evf to 1.4.1
- LP: #1536474
  * i40e: fix: do not sleep in netdev_ops
- LP: #1536474
  * i40e: remove unused argument
- LP: #1536474
  * i40evf: increase max number of queues
- LP: #1536474
  * i40evf: set real num queues
- LP: #1536474
  * i40evf: remove duplicate string
- LP: #1536474
  * i40e: Detection and recovery of TX queue hung logic moved to
service_task from tx_timeout
- LP: #1536474
  * i40e: Fix memory leaks, sideband filter programming
- LP: #1536474
  * i40evf: don't use atomic allocation
- LP: #1536474
  * i40e: propagate properly
- LP: #1536474
  * i40evf: use correct types
- LP: #1536474
  * i40e: use priv flags to control packet split
- LP: #1536474
  * i40e: Remove separate functions gathering XOFF Rx stats
- LP: #1536474
  * i40e: fix whitespace
- LP: #1536474
  * i40e/i40evf: use logical operator
- LP: #1536474
  * i40e/i40evf: Bump version to 1.4.7 for i40e and 1.4.3 for i40evf
- LP: #1536474
  * i40e: trivial fixes
- LP: #1536474
  * i40e: Fix i40e_print_features() VEB mode output
- LP: #1536474
  * i40e: chomp the 

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.2.0-27.32

---
linux (4.2.0-27.32) wily; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1536867

  [ Andy Whitcroft ]

  * SAUCE: (no-up) add compat_uts_machine= kernel command line override
- LP: #1520627

  [ Colin Ian King ]

  * SAUCE: (no-up) ACPI / tables: Add acpi_force_32bit_fadt_addr option to
force 32 bit FADT addresses
- LP: #1529381

  [ Eric Dumazet ]

  * SAUCE: (no-up) udp: properly support MSG_PEEK with truncated buffers
- LP: #1527902

  [ Guilherme G. Piccoli ]

  * SAUCE: powerpc/eeh: Validate arch in eeh_add_device_early()
- LP: #1486180

  [ Tim Gardner ]

  * SAUCE: (no-up) Revert "[SCSI] libiscsi: Reduce locking contention in
fast path"
- LP: #1517142
  * [Config] Add DRM ast driver to udeb installer image
- LP: #1514711

  [ Upstream Kernel Changes ]

  * net/mlx5e: Re-eanble client vlan TX acceleration
- LP: #1533249
  * net/mlx5e: Fix LSO vlan insertion
- LP: #1533249
  * net/mlx5e: Fix inline header size calculation
- LP: #1533249
  * net: usb: cdc_ncm: Adding Dell DW5812 LTE Verizon Mobile Broadband Card
- LP: #1533118
  * net: usb: cdc_ncm: Adding Dell DW5813 LTE AT Mobile Broadband Card
- LP: #1533118
  * powerpc/eeh: Fix recursive fenced PHB on Broadcom shiner adapter
- LP: #1532942

linux (4.2.0-26.31) wily; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1535795
  * Merged back Ubuntu-4.2.0-25.30

 -- Brad Figg   Thu, 21 Jan 2016 18:44:37 -0800

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

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 3.19.0-49.55

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

  [ Brad Figg ]

  * Release Tracking Bug
- LP: #1536775

  [ Colin Ian King ]

  * SAUCE: (no-up) ACPI / tables: Add acpi_force_32bit_fadt_addr option to
force 32 bit FADT addresses
- LP: #1529381

  [ Tim Gardner ]

  * [Config] Add DRM ast driver to udeb installer image
- LP: #1514711
  * SAUCE: (no-up) Revert "[SCSI] libiscsi: Reduce locking contention in
fast path"
- LP: #1517142

  [ Upstream Kernel Changes ]

  * powerpc/eeh: Fix recursive fenced PHB on Broadcom shiner adapter
- LP: #1532942
  * Drivers: hv: vmbus: prevent cpu offlining on newer hypervisors
- LP: #1440103
  * Drivers: hv: vmbus: teardown hv_vmbus_con workqueue and
vmbus_connection pages on shutdown
- LP: #1440103
  * drivers: hv: vmbus: Teardown synthetic interrupt controllers on module
unload
- LP: #1440103
  * clockevents: export clockevents_unbind_device instead of
clockevents_unbind
- LP: #1440103
  * Drivers: hv: vmbus: Teardown clockevent devices on module unload
- LP: #1440103
  * Drivers: hv: vmbus: Add support for VMBus panic notifier handler
- LP: #1440103
  * hv: run non-blocking message handlers in the dispatch tasklet
- LP: #1440103
  * Drivers: hv: vmbus: unregister panic notifier on module unload
- LP: #1440103
  * Drivers: hv: vmbus: Implement the protocol for tearing down vmbus state
- LP: #1440103
  * kexec: define kexec_in_progress in !CONFIG_KEXEC case
- LP: #1440103
  * Drivers: hv: vmbus: add special kexec handler
- LP: #1440103
  * Drivers: hv: don't do hypercalls when hypercall_page is NULL
- LP: #1440103
  * Drivers: hv: vmbus: add special crash handler
- LP: #1440103
  * Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
- LP: #1440103
  * hyperv: Implement netvsc_get_channels() ethool op
- LP: #1494423
  * hv_netvsc: Properly size the vrss queues
- LP: #1494423
  * hv_netvsc: Allocate the sendbuf in a NUMA aware way
- LP: #1494423
  * hv_netvsc: Allocate the receive buffer from the correct NUMA node
- LP: #1494423
  * Drivers: hv: vmbus: Implement NUMA aware CPU affinity for channels
- LP: #1494423
  * Drivers: hv: vmbus: Allocate ring buffer memory in NUMA aware fashion
- LP: #1494423
  * Drivers: hv: vmbus: Improve the CPU affiliation for channels
- LP: #1494423
  * Drivers: hv: vmbus: Further improve CPU affiliation logic
- LP: #1494423

linux (3.19.0-48.54) vivid; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
- LP: #1536124
  * Merged back Ubuntu-3.19.0-46.52

 -- Brad Figg   Thu, 21 Jan 2016 12:29:48 -0800

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

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

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

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Brad Figg]

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

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  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

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Luis Henriques]

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-
wily' to 'verification-done-wily'.

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  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

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Luis Henriques]

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 verification-needed-wily

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  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

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Tim Gardner]

Vivid 3.19.0-49.55
Wily 4.2.0-27.32

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  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

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Brad Figg]

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

** 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/1517142

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Tim Gardner]

That commit has now been reverted in Vivid, Wily, and Xenial.

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
 Assignee: Taco Screen team (taco-screen-team)
   Status: Triaged

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

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

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => 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/1517142

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  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

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Tim Gardner]

What kernel versions are affected ? Commit
659743b02c411075b26601725947b21df0bb29c8. has been mainline since v3.15

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Michael Hohnbaum]

IBM, any updates on the recommended fix for this issue?

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[bugproxy]

** Tags removed: severity-critical
** Tags added: severity-high

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Christopher M. Penalver]

** Tags added: bisect-done

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

** Changed in: linux (Ubuntu)
   Status: New => Triaged

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1517142] Re: ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

[Luciano Chavez]

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
  ubuntu guest with 10G n/w and Texan iSCSI crashes during FIO

Status in linux package in Ubuntu:
  New

Bug description:
  Issues were found in iSCSI tests with hardware remote targets.
  Specifically, kernel crash happens due to dereferencing a null pointer
  (sc->device->lun at libiscsi.c:369, with sc==NULL). During the crash,
  lots of messages regarding lists invalid accesses are showed in kernel
  log.

  The commit 659743b02c41 ("[SCSI] libiscsi: Reduce locking contention
  in fast path") appears to be the cause.

  Reverting the commit solve the issue, at least until we can discuss and
  find the exact problem (and its solution) in the commit
  659743b02c41 ("[SCSI] libiscsi: Reduce locking contention in fast path").

  A test kernel was patched to revert the offend commit - Prashantha is
  running tests to check if the problem is solved.

  With the patched kernel, I am unable to recreate the crash. The patch appears
  to be working.

  A discussion is ongoing in linux-scsi mailing list, to revert the
  patch upstream (look the following link).

  http://marc.info/?l=linux-scsi=144730474819919

  Another quick discussion, started by me, it's on open-iscsi mailing
  list, on Google Groups:

  https://groups.google.com/forum/#!topic/open-iscsi/0S5fEM_Aafk

  The iscsi maintainer wants to revert, but patch co-author wants more
  study before reverting. Prashantha is performing some performance
  analysis to check the impact of the patch on iscsi performance.

  Mirroring to Launchpad for Canonical's awareness. Once the discussion
  settles on the final solution, a patch or link to the upstream commit
  will be provided for Canonical to review for acceptance in the 14.04
  LTS kernel and SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517142/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp