From: Christoph Hellwig <hch@lst.de>
To: Marc Orr <marcorr@google.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-nvme@lists.infradead.org
Subject: Re: [PATCH 2/2] nvme-pci: fix error unwind in nvme_map_data
Date: Wed, 20 Jan 2021 17:48:24 +0100 [thread overview]
Message-ID: <20210120164824.GA21874@lst.de> (raw)
In-Reply-To: <CAA03e5Hb49rpNq2A8hmvo6tVrLnon0yAUiZvWvd8THCXyDQ-kg@mail.gmail.com>
On Wed, Jan 20, 2021 at 07:23:39AM -0800, Marc Orr wrote:
> On Wed, Jan 20, 2021 at 1:49 AM Christoph Hellwig <hch@lst.de> wrote:
> >
> > Properly unwind step by step using refactored helpers from nvme_unmap_data
> > to avoid a potential double dma_unmap on a mapping failure.
> >
> > Reported-by: Marc Orr <marcorr@google.com>
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Should these patches go to stable?
Yes. I've added the proper fixes tag:
Fixes: 7fe07d14f71f ("nvme-pci: merge nvme_free_iod into nvme_unmap_data")
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-20 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 9:49 fix error unwinding in nvme_map_data Christoph Hellwig
2021-01-20 9:49 ` [PATCH 1/2] nvme-pci: refactor nvme_unmap_data Christoph Hellwig
2021-01-20 15:19 ` Marc Orr
2021-01-20 9:49 ` [PATCH 2/2] nvme-pci: fix error unwind in nvme_map_data Christoph Hellwig
2021-01-20 15:23 ` Marc Orr
2021-01-20 16:48 ` Christoph Hellwig [this message]
2021-01-20 17:42 ` Keith Busch
2021-01-20 17:56 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210120164824.GA21874@lst.de \
--to=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=marcorr@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox