]> git.ipfire.org Git - thirdparty/kernel/stable-queue.git/commitdiff
4.9-stable patches
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 10 Sep 2017 11:37:32 +0000 (13:37 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sun, 10 Sep 2017 11:37:32 +0000 (13:37 +0200)
added patches:
alsa-msnd-optimize-harden-dsp-and-midi-loops.patch
btrfs-resume-qgroup-rescan-on-rw-remount.patch
locktorture-fix-potential-memory-leak-with-rw-lock-test.patch
mm-memory.c-fix-mem_cgroup_oom_disable-call-missing.patch
mtd-nand-mxc-fix-mxc_v1-ooblayout.patch
mtd-nand-qcom-fix-config-error-for-bch.patch
mtd-nand-qcom-fix-read-failure-without-complete-bootchain.patch
nvme-fabrics-generate-spec-compliant-uuid-nqns.patch
selftests-x86-fsgsbase-test-selectors-1-2-and-3.patch

queue-4.9/alsa-msnd-optimize-harden-dsp-and-midi-loops.patch [new file with mode: 0644]
queue-4.9/btrfs-resume-qgroup-rescan-on-rw-remount.patch [new file with mode: 0644]
queue-4.9/locktorture-fix-potential-memory-leak-with-rw-lock-test.patch [new file with mode: 0644]
queue-4.9/mm-memory.c-fix-mem_cgroup_oom_disable-call-missing.patch [new file with mode: 0644]
queue-4.9/mtd-nand-mxc-fix-mxc_v1-ooblayout.patch [new file with mode: 0644]
queue-4.9/mtd-nand-qcom-fix-config-error-for-bch.patch [new file with mode: 0644]
queue-4.9/mtd-nand-qcom-fix-read-failure-without-complete-bootchain.patch [new file with mode: 0644]
queue-4.9/nvme-fabrics-generate-spec-compliant-uuid-nqns.patch [new file with mode: 0644]
queue-4.9/selftests-x86-fsgsbase-test-selectors-1-2-and-3.patch [new file with mode: 0644]

diff --git a/queue-4.9/alsa-msnd-optimize-harden-dsp-and-midi-loops.patch b/queue-4.9/alsa-msnd-optimize-harden-dsp-and-midi-loops.patch
new file mode 100644 (file)
index 0000000..abc8b2b
--- /dev/null
@@ -0,0 +1,106 @@
+From 20e2b791796bd68816fa115f12be5320de2b8021 Mon Sep 17 00:00:00 2001
+From: Takashi Iwai <tiwai@suse.de>
+Date: Thu, 6 Jul 2017 12:34:40 +0200
+Subject: ALSA: msnd: Optimize / harden DSP and MIDI loops
+
+From: Takashi Iwai <tiwai@suse.de>
+
+commit 20e2b791796bd68816fa115f12be5320de2b8021 upstream.
+
+The ISA msnd drivers have loops fetching the ring-buffer head, tail
+and size values inside the loops.  Such codes are inefficient and
+fragile.
+
+This patch optimizes it, and also adds the sanity check to avoid the
+endless loops.
+
+Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=196131
+Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=196133
+Signed-off-by: Takashi Iwai <tiwai@suse.de>
+Signed-off-by: grygorii tertychnyi <gtertych@cisco.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ sound/isa/msnd/msnd_midi.c     |   28 ++++++++++++++--------------
+ sound/isa/msnd/msnd_pinnacle.c |   23 ++++++++++++-----------
+ 2 files changed, 26 insertions(+), 25 deletions(-)
+
+--- a/sound/isa/msnd/msnd_midi.c
++++ b/sound/isa/msnd/msnd_midi.c
+@@ -120,24 +120,24 @@ void snd_msndmidi_input_read(void *mpuv)
+       unsigned long flags;
+       struct snd_msndmidi *mpu = mpuv;
+       void *pwMIDQData = mpu->dev->mappedbase + MIDQ_DATA_BUFF;
++      u16 head, tail, size;
+       spin_lock_irqsave(&mpu->input_lock, flags);
+-      while (readw(mpu->dev->MIDQ + JQS_wTail) !=
+-             readw(mpu->dev->MIDQ + JQS_wHead)) {
+-              u16 wTmp, val;
+-              val = readw(pwMIDQData + 2 * readw(mpu->dev->MIDQ + JQS_wHead));
++      head = readw(mpu->dev->MIDQ + JQS_wHead);
++      tail = readw(mpu->dev->MIDQ + JQS_wTail);
++      size = readw(mpu->dev->MIDQ + JQS_wSize);
++      if (head > size || tail > size)
++              goto out;
++      while (head != tail) {
++              unsigned char val = readw(pwMIDQData + 2 * head);
+-                      if (test_bit(MSNDMIDI_MODE_BIT_INPUT_TRIGGER,
+-                                   &mpu->mode))
+-                              snd_rawmidi_receive(mpu->substream_input,
+-                                                  (unsigned char *)&val, 1);
+-
+-              wTmp = readw(mpu->dev->MIDQ + JQS_wHead) + 1;
+-              if (wTmp > readw(mpu->dev->MIDQ + JQS_wSize))
+-                      writew(0,  mpu->dev->MIDQ + JQS_wHead);
+-              else
+-                      writew(wTmp,  mpu->dev->MIDQ + JQS_wHead);
++              if (test_bit(MSNDMIDI_MODE_BIT_INPUT_TRIGGER, &mpu->mode))
++                      snd_rawmidi_receive(mpu->substream_input, &val, 1);
++              if (++head > size)
++                      head = 0;
++              writew(head, mpu->dev->MIDQ + JQS_wHead);
+       }
++ out:
+       spin_unlock_irqrestore(&mpu->input_lock, flags);
+ }
+ EXPORT_SYMBOL(snd_msndmidi_input_read);
+--- a/sound/isa/msnd/msnd_pinnacle.c
++++ b/sound/isa/msnd/msnd_pinnacle.c
+@@ -170,23 +170,24 @@ static irqreturn_t snd_msnd_interrupt(in
+ {
+       struct snd_msnd *chip = dev_id;
+       void *pwDSPQData = chip->mappedbase + DSPQ_DATA_BUFF;
++      u16 head, tail, size;
+       /* Send ack to DSP */
+       /* inb(chip->io + HP_RXL); */
+       /* Evaluate queued DSP messages */
+-      while (readw(chip->DSPQ + JQS_wTail) != readw(chip->DSPQ + JQS_wHead)) {
+-              u16 wTmp;
+-
+-              snd_msnd_eval_dsp_msg(chip,
+-                      readw(pwDSPQData + 2 * readw(chip->DSPQ + JQS_wHead)));
+-
+-              wTmp = readw(chip->DSPQ + JQS_wHead) + 1;
+-              if (wTmp > readw(chip->DSPQ + JQS_wSize))
+-                      writew(0, chip->DSPQ + JQS_wHead);
+-              else
+-                      writew(wTmp, chip->DSPQ + JQS_wHead);
++      head = readw(chip->DSPQ + JQS_wHead);
++      tail = readw(chip->DSPQ + JQS_wTail);
++      size = readw(chip->DSPQ + JQS_wSize);
++      if (head > size || tail > size)
++              goto out;
++      while (head != tail) {
++              snd_msnd_eval_dsp_msg(chip, readw(pwDSPQData + 2 * head));
++              if (++head > size)
++                      head = 0;
++              writew(head, chip->DSPQ + JQS_wHead);
+       }
++ out:
+       /* Send ack to DSP */
+       inb(chip->io + HP_RXL);
+       return IRQ_HANDLED;
diff --git a/queue-4.9/btrfs-resume-qgroup-rescan-on-rw-remount.patch b/queue-4.9/btrfs-resume-qgroup-rescan-on-rw-remount.patch
new file mode 100644 (file)
index 0000000..07a7854
--- /dev/null
@@ -0,0 +1,43 @@
+From 6c6b5a39c4bf3dbd8cf629c9f5450e983c19dbb9 Mon Sep 17 00:00:00 2001
+From: Aleksa Sarai <asarai@suse.de>
+Date: Tue, 4 Jul 2017 21:49:06 +1000
+Subject: btrfs: resume qgroup rescan on rw remount
+
+From: Aleksa Sarai <asarai@suse.de>
+
+commit 6c6b5a39c4bf3dbd8cf629c9f5450e983c19dbb9 upstream.
+
+Several distributions mount the "proper root" as ro during initrd and
+then remount it as rw before pivot_root(2). Thus, if a rescan had been
+aborted by a previous shutdown, the rescan would never be resumed.
+
+This issue would manifest itself as several btrfs ioctl(2)s causing the
+entire machine to hang when btrfs_qgroup_wait_for_completion was hit
+(due to the fs_info->qgroup_rescan_running flag being set but the rescan
+itself not being resumed). Notably, Docker's btrfs storage driver makes
+regular use of BTRFS_QUOTA_CTL_DISABLE and BTRFS_IOC_QUOTA_RESCAN_WAIT
+(causing this problem to be manifested on boot for some machines).
+
+Cc: Jeff Mahoney <jeffm@suse.com>
+Fixes: b382a324b60f ("Btrfs: fix qgroup rescan resume on mount")
+Signed-off-by: Aleksa Sarai <asarai@suse.de>
+Reviewed-by: Nikolay Borisov <nborisov@suse.com>
+Tested-by: Nikolay Borisov <nborisov@suse.com>
+Signed-off-by: David Sterba <dsterba@suse.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ fs/btrfs/super.c |    2 ++
+ 1 file changed, 2 insertions(+)
+
+--- a/fs/btrfs/super.c
++++ b/fs/btrfs/super.c
+@@ -1834,6 +1834,8 @@ static int btrfs_remount(struct super_bl
+                       goto restore;
+               }
++              btrfs_qgroup_rescan_resume(fs_info);
++
+               if (!fs_info->uuid_root) {
+                       btrfs_info(fs_info, "creating UUID tree");
+                       ret = btrfs_create_uuid_tree(fs_info);
diff --git a/queue-4.9/locktorture-fix-potential-memory-leak-with-rw-lock-test.patch b/queue-4.9/locktorture-fix-potential-memory-leak-with-rw-lock-test.patch
new file mode 100644 (file)
index 0000000..7670f47
--- /dev/null
@@ -0,0 +1,88 @@
+From f4dbba591945dc301c302672adefba9e2ec08dc5 Mon Sep 17 00:00:00 2001
+From: Yang Shi <yang.shi@linaro.org>
+Date: Thu, 10 Nov 2016 13:06:39 -0800
+Subject: locktorture: Fix potential memory leak with rw lock test
+
+From: Yang Shi <yang.shi@linaro.org>
+
+commit f4dbba591945dc301c302672adefba9e2ec08dc5 upstream.
+
+When running locktorture module with the below commands with kmemleak enabled:
+
+$ modprobe locktorture torture_type=rw_lock_irq
+$ rmmod locktorture
+
+The below kmemleak got caught:
+
+root@10:~# echo scan > /sys/kernel/debug/kmemleak
+[  323.197029] kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
+root@10:~# cat /sys/kernel/debug/kmemleak
+unreferenced object 0xffffffc07592d500 (size 128):
+  comm "modprobe", pid 368, jiffies 4294924118 (age 205.824s)
+  hex dump (first 32 bytes):
+    00 00 00 00 00 00 00 00 c3 7b 02 00 00 00 00 00  .........{......
+    00 00 00 00 00 00 00 00 d7 9b 02 00 00 00 00 00  ................
+  backtrace:
+    [<ffffff80081e5a88>] create_object+0x110/0x288
+    [<ffffff80086c6078>] kmemleak_alloc+0x58/0xa0
+    [<ffffff80081d5acc>] __kmalloc+0x234/0x318
+    [<ffffff80006fa130>] 0xffffff80006fa130
+    [<ffffff8008083ae4>] do_one_initcall+0x44/0x138
+    [<ffffff800817e28c>] do_init_module+0x68/0x1cc
+    [<ffffff800811c848>] load_module+0x1a68/0x22e0
+    [<ffffff800811d340>] SyS_finit_module+0xe0/0xf0
+    [<ffffff80080836f0>] el0_svc_naked+0x24/0x28
+    [<ffffffffffffffff>] 0xffffffffffffffff
+unreferenced object 0xffffffc07592d480 (size 128):
+  comm "modprobe", pid 368, jiffies 4294924118 (age 205.824s)
+  hex dump (first 32 bytes):
+    00 00 00 00 00 00 00 00 3b 6f 01 00 00 00 00 00  ........;o......
+    00 00 00 00 00 00 00 00 23 6a 01 00 00 00 00 00  ........#j......
+  backtrace:
+    [<ffffff80081e5a88>] create_object+0x110/0x288
+    [<ffffff80086c6078>] kmemleak_alloc+0x58/0xa0
+    [<ffffff80081d5acc>] __kmalloc+0x234/0x318
+    [<ffffff80006fa22c>] 0xffffff80006fa22c
+    [<ffffff8008083ae4>] do_one_initcall+0x44/0x138
+    [<ffffff800817e28c>] do_init_module+0x68/0x1cc
+    [<ffffff800811c848>] load_module+0x1a68/0x22e0
+    [<ffffff800811d340>] SyS_finit_module+0xe0/0xf0
+    [<ffffff80080836f0>] el0_svc_naked+0x24/0x28
+    [<ffffffffffffffff>] 0xffffffffffffffff
+
+It is because cxt.lwsa and cxt.lrsa don't get freed in module_exit, so free
+them in lock_torture_cleanup() and free writer_tasks if reader_tasks is
+failed at memory allocation.
+
+Signed-off-by: Yang Shi <yang.shi@linaro.org>
+Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
+Reviewed-by: Josh Triplett <josh@joshtriplett.org>
+Cc: 石洋 <yang.s@alibaba-inc.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ kernel/locking/locktorture.c |    6 ++++++
+ 1 file changed, 6 insertions(+)
+
+--- a/kernel/locking/locktorture.c
++++ b/kernel/locking/locktorture.c
+@@ -780,6 +780,10 @@ static void lock_torture_cleanup(void)
+       else
+               lock_torture_print_module_parms(cxt.cur_ops,
+                                               "End of test: SUCCESS");
++
++      kfree(cxt.lwsa);
++      kfree(cxt.lrsa);
++
+ end:
+       torture_cleanup_end();
+ }
+@@ -924,6 +928,8 @@ static int __init lock_torture_init(void
+                                      GFP_KERNEL);
+               if (reader_tasks == NULL) {
+                       VERBOSE_TOROUT_ERRSTRING("reader_tasks: Out of memory");
++                      kfree(writer_tasks);
++                      writer_tasks = NULL;
+                       firsterr = -ENOMEM;
+                       goto unwind;
+               }
diff --git a/queue-4.9/mm-memory.c-fix-mem_cgroup_oom_disable-call-missing.patch b/queue-4.9/mm-memory.c-fix-mem_cgroup_oom_disable-call-missing.patch
new file mode 100644 (file)
index 0000000..b4f5213
--- /dev/null
@@ -0,0 +1,55 @@
+From de0c799bba2610a8e1e9a50d76a28614520a4cd4 Mon Sep 17 00:00:00 2001
+From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
+Date: Fri, 8 Sep 2017 16:13:12 -0700
+Subject: mm/memory.c: fix mem_cgroup_oom_disable() call missing
+
+From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
+
+commit de0c799bba2610a8e1e9a50d76a28614520a4cd4 upstream.
+
+Seen while reading the code, in handle_mm_fault(), in the case
+arch_vma_access_permitted() is failing the call to
+mem_cgroup_oom_disable() is not made.
+
+To fix that, move the call to mem_cgroup_oom_enable() after calling
+arch_vma_access_permitted() as it should not have entered the memcg OOM.
+
+Link: http://lkml.kernel.org/r/1504625439-31313-1-git-send-email-ldufour@linux.vnet.ibm.com
+Fixes: bae473a423f6 ("mm: introduce fault_env")
+Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
+Acked-by: Kirill A. Shutemov <kirill@shutemov.name>
+Acked-by: Michal Hocko <mhocko@suse.com>
+Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
+Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ mm/memory.c |   10 +++++-----
+ 1 file changed, 5 insertions(+), 5 deletions(-)
+
+--- a/mm/memory.c
++++ b/mm/memory.c
+@@ -3596,6 +3596,11 @@ int handle_mm_fault(struct vm_area_struc
+       /* do counter updates before entering really critical section. */
+       check_sync_rss_stat(current);
++      if (!arch_vma_access_permitted(vma, flags & FAULT_FLAG_WRITE,
++                                          flags & FAULT_FLAG_INSTRUCTION,
++                                          flags & FAULT_FLAG_REMOTE))
++              return VM_FAULT_SIGSEGV;
++
+       /*
+        * Enable the memcg OOM handling for faults triggered in user
+        * space.  Kernel faults are handled more gracefully.
+@@ -3603,11 +3608,6 @@ int handle_mm_fault(struct vm_area_struc
+       if (flags & FAULT_FLAG_USER)
+               mem_cgroup_oom_enable();
+-      if (!arch_vma_access_permitted(vma, flags & FAULT_FLAG_WRITE,
+-                                          flags & FAULT_FLAG_INSTRUCTION,
+-                                          flags & FAULT_FLAG_REMOTE))
+-              return VM_FAULT_SIGSEGV;
+-
+       if (unlikely(is_vm_hugetlb_page(vma)))
+               ret = hugetlb_fault(vma->vm_mm, vma, address, flags);
+       else
diff --git a/queue-4.9/mtd-nand-mxc-fix-mxc_v1-ooblayout.patch b/queue-4.9/mtd-nand-mxc-fix-mxc_v1-ooblayout.patch
new file mode 100644 (file)
index 0000000..72511b4
--- /dev/null
@@ -0,0 +1,56 @@
+From 3bff08dffe3115a25ce04b95ea75f6d868572c60 Mon Sep 17 00:00:00 2001
+From: Boris Brezillon <boris.brezillon@free-electrons.com>
+Date: Fri, 25 Nov 2016 11:32:32 +0100
+Subject: mtd: nand: mxc: Fix mxc_v1 ooblayout
+
+From: Boris Brezillon <boris.brezillon@free-electrons.com>
+
+commit 3bff08dffe3115a25ce04b95ea75f6d868572c60 upstream.
+
+Commit a894cf6c5a82 ("mtd: nand: mxc: switch to mtd_ooblayout_ops")
+introduced a bug in the OOB layout description. Even if the driver claims
+that 3 ECC bytes are reserved to protect 512 bytes of data, it's actually
+5 ECC bytes to protect 512+6 bytes of data (some OOB bytes are also
+protected using extra ECC bytes).
+
+Fix the mxc_v1_ooblayout_{free,ecc}() functions to reflect this behavior.
+
+Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
+Fixes: a894cf6c5a82 ("mtd: nand: mxc: switch to mtd_ooblayout_ops")
+Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ drivers/mtd/nand/mxc_nand.c |    7 ++++---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+--- a/drivers/mtd/nand/mxc_nand.c
++++ b/drivers/mtd/nand/mxc_nand.c
+@@ -877,6 +877,8 @@ static void mxc_do_addr_cycle(struct mtd
+       }
+ }
++#define MXC_V1_ECCBYTES               5
++
+ static int mxc_v1_ooblayout_ecc(struct mtd_info *mtd, int section,
+                               struct mtd_oob_region *oobregion)
+ {
+@@ -886,7 +888,7 @@ static int mxc_v1_ooblayout_ecc(struct m
+               return -ERANGE;
+       oobregion->offset = (section * 16) + 6;
+-      oobregion->length = nand_chip->ecc.bytes;
++      oobregion->length = MXC_V1_ECCBYTES;
+       return 0;
+ }
+@@ -908,8 +910,7 @@ static int mxc_v1_ooblayout_free(struct
+                       oobregion->length = 4;
+               }
+       } else {
+-              oobregion->offset = ((section - 1) * 16) +
+-                                  nand_chip->ecc.bytes + 6;
++              oobregion->offset = ((section - 1) * 16) + MXC_V1_ECCBYTES + 6;
+               if (section < nand_chip->ecc.steps)
+                       oobregion->length = (section * 16) + 6 -
+                                           oobregion->offset;
diff --git a/queue-4.9/mtd-nand-qcom-fix-config-error-for-bch.patch b/queue-4.9/mtd-nand-qcom-fix-config-error-for-bch.patch
new file mode 100644 (file)
index 0000000..89e0851
--- /dev/null
@@ -0,0 +1,39 @@
+From 10777de570016471fd929869c7830a7772893e39 Mon Sep 17 00:00:00 2001
+From: Abhishek Sahu <absahu@codeaurora.org>
+Date: Thu, 3 Aug 2017 17:56:39 +0200
+Subject: mtd: nand: qcom: fix config error for BCH
+
+From: Abhishek Sahu <absahu@codeaurora.org>
+
+commit 10777de570016471fd929869c7830a7772893e39 upstream.
+
+The configuration for BCH is not correct in the current driver.
+The ECC_CFG_ECC_DISABLE bit defines whether to enable or disable the
+BCH ECC in which
+
+       0x1 : BCH_DISABLED
+       0x0 : BCH_ENABLED
+
+But currently host->bch_enabled is being assigned to BCH_DISABLED.
+
+Fixes: c76b78d8ec05a ("mtd: nand: Qualcomm NAND controller driver")
+Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
+Reviewed-by: Archit Taneja <architt@codeaurora.org>
+Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ drivers/mtd/nand/qcom_nandc.c |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/drivers/mtd/nand/qcom_nandc.c
++++ b/drivers/mtd/nand/qcom_nandc.c
+@@ -1900,7 +1900,7 @@ static int qcom_nand_host_setup(struct q
+                               | wide_bus << WIDE_FLASH
+                               | 1 << DEV0_CFG1_ECC_DISABLE;
+-      host->ecc_bch_cfg = host->bch_enabled << ECC_CFG_ECC_DISABLE
++      host->ecc_bch_cfg = !host->bch_enabled << ECC_CFG_ECC_DISABLE
+                               | 0 << ECC_SW_RESET
+                               | host->cw_data << ECC_NUM_DATA_BYTES
+                               | 1 << ECC_FORCE_CLK_OPEN
diff --git a/queue-4.9/mtd-nand-qcom-fix-read-failure-without-complete-bootchain.patch b/queue-4.9/mtd-nand-qcom-fix-read-failure-without-complete-bootchain.patch
new file mode 100644 (file)
index 0000000..73cba68
--- /dev/null
@@ -0,0 +1,81 @@
+From d8a9b320a26c1ea28e51e4f3ecfb593d5aac2910 Mon Sep 17 00:00:00 2001
+From: Abhishek Sahu <absahu@codeaurora.org>
+Date: Fri, 11 Aug 2017 17:09:16 +0530
+Subject: mtd: nand: qcom: fix read failure without complete bootchain
+
+From: Abhishek Sahu <absahu@codeaurora.org>
+
+commit d8a9b320a26c1ea28e51e4f3ecfb593d5aac2910 upstream.
+
+The NAND page read fails without complete boot chain since
+NAND_DEV_CMD_VLD value is not proper. The default power on reset
+value for this register is
+
+    0xe - ERASE_START_VALID | WRITE_START_VALID | READ_STOP_VALID
+
+The READ_START_VALID should be enabled for sending PAGE_READ
+command. READ_STOP_VALID should be cleared since normal NAND
+page read does not require READ_STOP command.
+
+Fixes: c76b78d8ec05a ("mtd: nand: Qualcomm NAND controller driver")
+Reviewed-by: Archit Taneja <architt@codeaurora.org>
+Signed-off-by: Abhishek Sahu <absahu@codeaurora.org>
+Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ drivers/mtd/nand/qcom_nandc.c |   16 ++++++++++++----
+ 1 file changed, 12 insertions(+), 4 deletions(-)
+
+--- a/drivers/mtd/nand/qcom_nandc.c
++++ b/drivers/mtd/nand/qcom_nandc.c
+@@ -109,7 +109,11 @@
+ #define       READ_ADDR                       0
+ /* NAND_DEV_CMD_VLD bits */
+-#define       READ_START_VLD                  0
++#define       READ_START_VLD                  BIT(0)
++#define       READ_STOP_VLD                   BIT(1)
++#define       WRITE_START_VLD                 BIT(2)
++#define       ERASE_START_VLD                 BIT(3)
++#define       SEQ_READ_START_VLD              BIT(4)
+ /* NAND_EBI2_ECC_BUF_CFG bits */
+ #define       NUM_STEPS                       0
+@@ -148,6 +152,10 @@
+ #define       FETCH_ID                        0xb
+ #define       RESET_DEVICE                    0xd
++/* Default Value for NAND_DEV_CMD_VLD */
++#define NAND_DEV_CMD_VLD_VAL          (READ_START_VLD | WRITE_START_VLD | \
++                                       ERASE_START_VLD | SEQ_READ_START_VLD)
++
+ /*
+  * the NAND controller performs reads/writes with ECC in 516 byte chunks.
+  * the driver calls the chunks 'step' or 'codeword' interchangeably
+@@ -672,8 +680,7 @@ static int nandc_param(struct qcom_nand_
+       /* configure CMD1 and VLD for ONFI param probing */
+       nandc_set_reg(nandc, NAND_DEV_CMD_VLD,
+-                    (nandc->vld & ~(1 << READ_START_VLD))
+-                    | 0 << READ_START_VLD);
++                    (nandc->vld & ~READ_START_VLD));
+       nandc_set_reg(nandc, NAND_DEV_CMD1,
+                     (nandc->cmd1 & ~(0xFF << READ_ADDR))
+                     | NAND_CMD_PARAM << READ_ADDR);
+@@ -1972,13 +1979,14 @@ static int qcom_nandc_setup(struct qcom_
+ {
+       /* kill onenand */
+       nandc_write(nandc, SFLASHC_BURST_CFG, 0);
++      nandc_write(nandc, NAND_DEV_CMD_VLD, NAND_DEV_CMD_VLD_VAL);
+       /* enable ADM DMA */
+       nandc_write(nandc, NAND_FLASH_CHIP_SELECT, DM_EN);
+       /* save the original values of these registers */
+       nandc->cmd1 = nandc_read(nandc, NAND_DEV_CMD1);
+-      nandc->vld = nandc_read(nandc, NAND_DEV_CMD_VLD);
++      nandc->vld = NAND_DEV_CMD_VLD_VAL;
+       return 0;
+ }
diff --git a/queue-4.9/nvme-fabrics-generate-spec-compliant-uuid-nqns.patch b/queue-4.9/nvme-fabrics-generate-spec-compliant-uuid-nqns.patch
new file mode 100644 (file)
index 0000000..e84e9c9
--- /dev/null
@@ -0,0 +1,33 @@
+From 40a5fce495715c48c2e02668144e68a507ac5a30 Mon Sep 17 00:00:00 2001
+From: Daniel Verkamp <daniel.verkamp@intel.com>
+Date: Wed, 30 Aug 2017 15:18:19 -0700
+Subject: nvme-fabrics: generate spec-compliant UUID NQNs
+
+From: Daniel Verkamp <daniel.verkamp@intel.com>
+
+commit 40a5fce495715c48c2e02668144e68a507ac5a30 upstream.
+
+The default host NQN, which is generated based on the host's UUID,
+does not follow the UUID-based NQN format laid out in the NVMe 1.3
+specification.  Remove the "NVMf:" portion of the NQN to match the spec.
+
+Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com>
+Reviewed-by: Max Gurtovoy <maxg@mellanox.com>
+Signed-off-by: Christoph Hellwig <hch@lst.de>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ drivers/nvme/host/fabrics.c |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/drivers/nvme/host/fabrics.c
++++ b/drivers/nvme/host/fabrics.c
+@@ -77,7 +77,7 @@ static struct nvmf_host *nvmf_host_defau
+       kref_init(&host->ref);
+       uuid_be_gen(&host->id);
+       snprintf(host->nqn, NVMF_NQN_SIZE,
+-              "nqn.2014-08.org.nvmexpress:NVMf:uuid:%pUb", &host->id);
++              "nqn.2014-08.org.nvmexpress:uuid:%pUb", &host->id);
+       mutex_lock(&nvmf_hosts_mutex);
+       list_add_tail(&host->list, &nvmf_hosts);
diff --git a/queue-4.9/selftests-x86-fsgsbase-test-selectors-1-2-and-3.patch b/queue-4.9/selftests-x86-fsgsbase-test-selectors-1-2-and-3.patch
new file mode 100644 (file)
index 0000000..d85ff4f
--- /dev/null
@@ -0,0 +1,114 @@
+From 23d98c204386a98d9ef9f9e744f41443ece4929f Mon Sep 17 00:00:00 2001
+From: Andy Lutomirski <luto@kernel.org>
+Date: Tue, 1 Aug 2017 07:11:36 -0700
+Subject: selftests/x86/fsgsbase: Test selectors 1, 2, and 3
+
+From: Andy Lutomirski <luto@kernel.org>
+
+commit 23d98c204386a98d9ef9f9e744f41443ece4929f upstream.
+
+Those are funny cases.  Make sure they work.
+
+(Something is screwy with signal handling if a selector is 1, 2, or 3.
+Anyone who wants to dive into that rabbit hole is welcome to do so.)
+
+Signed-off-by: Andy Lutomirski <luto@kernel.org>
+Cc: Borislav Petkov <bp@alien8.de>
+Cc: Borislav Petkov <bpetkov@suse.de>
+Cc: Brian Gerst <brgerst@gmail.com>
+Cc: Chang Seok <chang.seok.bae@intel.com>
+Cc: Denys Vlasenko <dvlasenk@redhat.com>
+Cc: H. Peter Anvin <hpa@zytor.com>
+Cc: Josh Poimboeuf <jpoimboe@redhat.com>
+Cc: Linus Torvalds <torvalds@linux-foundation.org>
+Cc: Peter Zijlstra <peterz@infradead.org>
+Cc: Thomas Gleixner <tglx@linutronix.de>
+Signed-off-by: Ingo Molnar <mingo@kernel.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+
+---
+ tools/testing/selftests/x86/fsgsbase.c |   41 ++++++++++++++++++++++++++++-----
+ 1 file changed, 35 insertions(+), 6 deletions(-)
+
+--- a/tools/testing/selftests/x86/fsgsbase.c
++++ b/tools/testing/selftests/x86/fsgsbase.c
+@@ -285,9 +285,12 @@ static void *threadproc(void *ctx)
+       }
+ }
+-static void set_gs_and_switch_to(unsigned long local, unsigned long remote)
++static void set_gs_and_switch_to(unsigned long local,
++                               unsigned short force_sel,
++                               unsigned long remote)
+ {
+       unsigned long base;
++      unsigned short sel_pre_sched, sel_post_sched;
+       bool hard_zero = false;
+       if (local == HARD_ZERO) {
+@@ -297,6 +300,8 @@ static void set_gs_and_switch_to(unsigne
+       printf("[RUN]\tARCH_SET_GS(0x%lx)%s, then schedule to 0x%lx\n",
+              local, hard_zero ? " and clear gs" : "", remote);
++      if (force_sel)
++              printf("\tBefore schedule, set selector to 0x%hx\n", force_sel);
+       if (syscall(SYS_arch_prctl, ARCH_SET_GS, local) != 0)
+               err(1, "ARCH_SET_GS");
+       if (hard_zero)
+@@ -307,18 +312,35 @@ static void set_gs_and_switch_to(unsigne
+               printf("[FAIL]\tGSBASE wasn't set as expected\n");
+       }
++      if (force_sel) {
++              asm volatile ("mov %0, %%gs" : : "rm" (force_sel));
++              sel_pre_sched = force_sel;
++              local = read_base(GS);
++
++              /*
++               * Signal delivery seems to mess up weird selectors.  Put it
++               * back.
++               */
++              asm volatile ("mov %0, %%gs" : : "rm" (force_sel));
++      } else {
++              asm volatile ("mov %%gs, %0" : "=rm" (sel_pre_sched));
++      }
++
+       remote_base = remote;
+       ftx = 1;
+       syscall(SYS_futex, &ftx, FUTEX_WAKE, 0, NULL, NULL, 0);
+       while (ftx != 0)
+               syscall(SYS_futex, &ftx, FUTEX_WAIT, 1, NULL, NULL, 0);
++      asm volatile ("mov %%gs, %0" : "=rm" (sel_post_sched));
+       base = read_base(GS);
+-      if (base == local) {
+-              printf("[OK]\tGSBASE remained 0x%lx\n", local);
++      if (base == local && sel_pre_sched == sel_post_sched) {
++              printf("[OK]\tGS/BASE remained 0x%hx/0x%lx\n",
++                     sel_pre_sched, local);
+       } else {
+               nerrs++;
+-              printf("[FAIL]\tGSBASE changed to 0x%lx\n", base);
++              printf("[FAIL]\tGS/BASE changed from 0x%hx/0x%lx to 0x%hx/0x%lx\n",
++                     sel_pre_sched, local, sel_post_sched, base);
+       }
+ }
+@@ -381,8 +403,15 @@ int main()
+       for (int local = 0; local < 4; local++) {
+               for (int remote = 0; remote < 4; remote++) {
+-                      set_gs_and_switch_to(bases_with_hard_zero[local],
+-                                           bases_with_hard_zero[remote]);
++                      for (unsigned short s = 0; s < 5; s++) {
++                              unsigned short sel = s;
++                              if (s == 4)
++                                      asm ("mov %%ss, %0" : "=rm" (sel));
++                              set_gs_and_switch_to(
++                                      bases_with_hard_zero[local],
++                                      sel,
++                                      bases_with_hard_zero[remote]);
++                      }
+               }
+       }