1. 30 Nov, 2018 1 commit
  2. 27 Nov, 2018 2 commits
  3. 09 Nov, 2018 1 commit
  4. 17 Oct, 2018 4 commits
  5. 08 Oct, 2018 1 commit
  6. 01 Oct, 2018 3 commits
  7. 28 Sep, 2018 2 commits
  8. 08 Aug, 2018 1 commit
  9. 30 Jul, 2018 2 commits
  10. 27 Jul, 2018 3 commits
  11. 23 Jul, 2018 2 commits
  12. 20 Jul, 2018 1 commit
  13. 17 Jul, 2018 2 commits
    • Weiping Zhang's avatar
      nvme: don't enable AEN if not supported · fa441b71
      Weiping Zhang authored
      Avoid excuting set_feature command if there is no supported bit in
      Optional Asynchronous Events Supported (OAES).
      
      Fixes: c0561f82 ("nvme: submit AEN event configuration on startup")
      Reviewed-by: default avatarSagi Grimberg <sagi@grimberg.me>
      Signed-off-by: default avatarWeiping Zhang <zhangweiping@didichuxing.com>
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      fa441b71
    • Scott Bauer's avatar
      nvme: ensure forward progress during Admin passthru · cf39a6bc
      Scott Bauer authored
      If the controller supports effects and goes down during the passthru admin
      command we will deadlock during namespace revalidation.
      
      [  363.488275] INFO: task kworker/u16:5:231 blocked for more than 120 seconds.
      [  363.488290]       Not tainted 4.17.0+ #2
      [  363.488296] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
      [  363.488303] kworker/u16:5   D    0   231      2 0x80000000
      [  363.488331] Workqueue: nvme-reset-wq nvme_reset_work [nvme]
      [  363.488338] Call Trace:
      [  363.488385]  schedule+0x75/0x190
      [  363.488396]  rwsem_down_read_failed+0x1c3/0x2f0
      [  363.488481]  call_rwsem_down_read_failed+0x14/0x30
      [  363.488504]  down_read+0x1d/0x80
      [  363.488523]  nvme_stop_queues+0x1e/0xa0 [nvme_core]
      [  363.488536]  nvme_dev_disable+0xae4/0x1620 [nvme]
      [  363.488614]  nvme_reset_work+0xd1e/0x49d9 [nvme]
      [  363.488911]  process_one_work+0x81a/0x1400
      [  363.488934]  worker_thread+0x87/0xe80
      [  363.488955]  kthread+0x2db/0x390
      [  363.488977]  ret_from_fork+0x35/0x40
      
      Fixes: 84fef62d ("nvme: check admin passthru command effects")
      Signed-off-by: default avatarScott Bauer <scott.bauer@intel.com>
      Reviewed-by: default avatarKeith Busch <keith.busch@linux.intel.com>
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      cf39a6bc
  14. 21 Jun, 2018 1 commit
    • Jens Axboe's avatar
      nvme-pci: limit max IO size and segments to avoid high order allocations · 943e942e
      Jens Axboe authored
      nvme requires an sg table allocation for each request. If the request
      is large, then the allocation can become quite large. For instance,
      with our default software settings of 1280KB IO size, we'll need
      10248 bytes of sg table. That turns into a 2nd order allocation,
      which we can't always guarantee. If we fail the allocation, blk-mq
      will retry it later. But there's no guarantee that we'll EVER be
      able to allocate that much contigious memory.
      
      Limit the IO size such that we never need more than a single page
      of memory. That's a lot faster and more reliable. Then back that
      allocation with a mempool, so that we know we'll always be able
      to succeed the allocation at some point.
      Signed-off-by: default avatarJens Axboe <axboe@kernel.dk>
      Acked-by: default avatarKeith Busch <keith.busch@intel.com>
      Signed-off-by: default avatarChristoph Hellwig <hch@lst.de>
      943e942e
  15. 14 Jun, 2018 1 commit
  16. 13 Jun, 2018 1 commit
  17. 11 Jun, 2018 1 commit
  18. 08 Jun, 2018 1 commit
  19. 01 Jun, 2018 3 commits
  20. 31 May, 2018 1 commit
  21. 30 May, 2018 1 commit
  22. 29 May, 2018 1 commit
  23. 25 May, 2018 2 commits
  24. 23 May, 2018 1 commit
  25. 18 May, 2018 1 commit