[Kernel-packages] [Bug 1681469] Re: Potential memory corruption with capi adapters

2021-02-11 Thread Tim Gardner 
** Changed in: linux (Ubuntu)
 Assignee: Tim Gardner (timg-tpi) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Tim Gardner (timg-tpi) => (unassigned)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Tim Gardner (timg-tpi) => (unassigned)

** Changed in: linux (Ubuntu Zesty)
 Assignee: Tim Gardner (timg-tpi) => (unassigned)

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2019-10-03 Thread Po-Hsu Lin 
** Changed in: linux (Ubuntu)
   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/1681469

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2019-07-24 Thread Brad Figg 
** Tags added: cscc

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2017-05-16 Thread Launchpad Bug Tracker 
This bug was fixed in the package linux - 4.8.0-52.55

---
linux (4.8.0-52.55) yakkety; urgency=low

  * linux: 4.8.0-52.55 -proposed tracker (LP: #1686976)

  * CVE-2017-7477: macsec: avoid heap overflow in skb_to_sgvec (LP: #1685892)
- macsec: avoid heap overflow in skb_to_sgvec
- macsec: dynamically allocate space for sglist

  * net/ipv4: original ingress device index set as the loopback interface.
(LP: #1683982)
- net: fix incorrect original ingress device index in PKTINFO

  * Touchpad not working correctly after kernel upgrade (LP: #1662589)
- Input: ALPS - fix V8+ protocol handling (73 03 28)

  * ifup service of network device stay active after driver stop (LP: #1672144)
- net: use net->count to check whether a netns is alive or not

  * [Hyper-V] mkfs regression in kernel 4.4+ (LP: #1682215)
- block: relax check on sg gap

  * Potential memory corruption with capi adapters (LP: #1681469)
- powerpc/mm: Add missing global TLB invalidate if cxl is active

  * [Hyper-V/Azure] Please include Mellanox OFED drivers in Azure kernel and
image (LP: #1650058)
- net/mlx4_en: Fix bad WQE issue
- net/mlx4_core: Fix racy CQ (Completion Queue) free
- net/mlx4_core: Fix when to save some qp context flags for dynamic VST to 
VGT
  transitions
- net/mlx4_core: Avoid command timeouts during VF driver device shutdown

 -- Stefan Bader   Fri, 28 Apr 2017 12:17:12
+0200

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

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

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2017-05-04 Thread bugproxy 
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2017-05-03 Thread Kleber Sacilotto de Souza 
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-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

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-yakkety

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2017-04-13 Thread Seth Forshee 
** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => 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/1681469

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in aa-series:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2017-04-13 Thread Stefan Bader 
Actually 4.4.60 upstream included this for Xenial.

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

** Changed in: linux (Ubuntu Yakkety)
   Status: In Progress => 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/1681469

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux source package in aa-series:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2017-04-12 Thread Tim Gardner 
https://lists.ubuntu.com/archives/kernel-team/2017-April/083582.html

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

** Also affects: linux (Ubuntu Aa-series)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Aa-series)
   Status: New => Fix Released

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

** Changed in: linux (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: linux (Ubuntu Zesty)
 Assignee: Taco Screen team (taco-screen-team) => Tim Gardner (timg-tpi)

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in aa-series:
  Fix Released

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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 1681469] Re: Potential memory corruption with capi adapters

2017-04-10 Thread bugproxy 
** Tags removed: severity-high
** Tags added: severity-critical

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

Title:
  Potential memory corruption with capi adapters

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Frederic Barrat  -
  2017-04-10 04:44:01 ==

  ---Problem Description---
  Memory corruption can be seen when using a capi adapter. It can happen if the 
host process allocates/frees/reallocates memory areas used by the the capi 
adapter.
  Some TLB invalidations may not be propagated to the capi adapter, causing the 
corruption.
   
  Contact Information = frederic.bar...@fr.ibm.com 
   
  ---uname output---
  Linux garri 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:05:15 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  capi card needed, with the AFU image used by libdonut development  

   
  Machine Type = Tuleta 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Run libdonut in a loop, until corruption is seen. Host process will dump core
   
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for frederic.bar...@fr.ibm.com: 
  -Attach sysctl -a output output to the bug.

  == Comment: #1 - Frederic Barrat  - 2017-04-10 
04:45:19 ==
  Fix is already upstream:

  commit 88b1bf7268f56887ca88eb09c6fb0f4fc970121a
  Author: Frederic Barrat 
  Date:   Wed Mar 29 19:19:42 2017 +0200

  powerpc/mm: Add missing global TLB invalidate if cxl is active


  Could it be backported to the 16.04 LTS release, as well as 17.04?
  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1681469/+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