On 12/21/2017 11:23 PM, Johannes Thumshirn wrote: > But a Fixes: and/or Cc: <stable at vger.kernel.org> might have been a > good Idea as well. > Fixes perhaps. The patch that introduced the issue (a0b69cc8e5caff3cb6442dfa807f47b44e716aad) is only in nvme-4.16, so it doesn't quite apply. -- james