Activity log for bug #1834119

Date Who What changed Old value New value Message
2019-06-25 02:04:04 quanxian bug added bug
2019-06-25 02:05:01 quanxian bug task added ndctl (Ubuntu)
2019-06-25 12:39:34 Andreas Hasenack bug added subscriber Andreas Hasenack
2019-06-25 23:41:28 quanxian affects ndctl (Ubuntu) linux (Ubuntu)
2019-06-26 00:00:06 Ubuntu Kernel Bot linux (Ubuntu): status New Incomplete
2019-06-26 00:00:08 Ubuntu Kernel Bot tags intel-upkg-19.10 eoan intel-upkg-19.10
2019-08-20 03:55:04 quanxian 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.2 Target Release: 19.10 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
2019-08-20 03:55:07 quanxian intel: status New Fix Committed
2019-10-23 06:50:17 quanxian intel: status Fix Committed Fix Released