87a30e1f05d7 driver-core, libnvdimm: Let device subsystems add local lockdep 
coverage
ca6bf264f6d8 libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock
b70d31d054ee libnvdimm/bus: Stop holding nvdimm_bus_list_mutex over __nd_ioctl()
6de5d06e657a libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
700cd033a82d libnvdimm/region: Register badblocks before namespaces
8aac0e233891 libnvdimm/bus: Prevent duplicate device_unregister() calls

** Description changed:

  Description:
  
  Patch: fix patch in the libnvdimm pending tree.
  Proposed fixes here: 
https://lists.01.org/pipermail/linux-nvdimm/2019-June/021847.html
  and pushed out to libnvdimm-pending: 
https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git/log/?h=libnvdimm-pending
- 
  
  Upstream Bug link: https://github.com/pmem/ndctl/issues/96
  
  The problem is fairly easy to reproduce in as little as 10 minutes.
  Do the following in parallel, like in separate terminals. Example...
  in term #1, #3, #5, type
  while [1]; do ndctl create-namespace -m devdax -s 48G done
  in term #2, #4, #6, type
  while [1]; do ndctl destroy-namespace all -f done
  
  Even simple invocation will eventually lead to a panic, it can take hours 
though. Example...
  in term #1 run the script
  #/bin/bash
  while /bin/true
  do
  ndctl destroy-namespace -f all
  date
  for R in ndctl list -R | jq -r ".[] | .dev"
  do
  for i in {1..10}
  do
  ndctl create-namespace -r $R -s 8g -m devdax
  done
  done
  done
  in term #2 type
  while /bin/true; do ndctl list done
  
  Run that same terminal #1 script in 2 separate terminals, thereby
  creating 2 separate threads that will destroy/create will usually result
  in a panic within an hour.
  
- Target Kernel: 5.2
+ Target Kernel: 5.3
  Target Release: 19.10

** Changed in: intel
       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/1834119

Title:
  [AEP-BUG] Critical:concurrent invocations of ndctl can cause linux
  panic

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  Patch: fix patch in the libnvdimm pending tree.
  Proposed fixes here: 
https://lists.01.org/pipermail/linux-nvdimm/2019-June/021847.html
  and pushed out to libnvdimm-pending: 
https://git.kernel.org/pub/scm/linux/kernel/git/djbw/nvdimm.git/log/?h=libnvdimm-pending

  Upstream Bug link: https://github.com/pmem/ndctl/issues/96

  The problem is fairly easy to reproduce in as little as 10 minutes.
  Do the following in parallel, like in separate terminals. Example...
  in term #1, #3, #5, type
  while [1]; do ndctl create-namespace -m devdax -s 48G done
  in term #2, #4, #6, type
  while [1]; do ndctl destroy-namespace all -f done

  Even simple invocation will eventually lead to a panic, it can take hours 
though. Example...
  in term #1 run the script
  #/bin/bash
  while /bin/true
  do
  ndctl destroy-namespace -f all
  date
  for R in ndctl list -R | jq -r ".[] | .dev"
  do
  for i in {1..10}
  do
  ndctl create-namespace -r $R -s 8g -m devdax
  done
  done
  done
  in term #2 type
  while /bin/true; do ndctl list done

  Run that same terminal #1 script in 2 separate terminals, thereby
  creating 2 separate threads that will destroy/create will usually
  result in a panic within an hour.

  Target Kernel: 5.3
  Target Release: 19.10

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

Reply via email to