From: Keith Busch <kbusch@kernel.org>
To: Keisuke Nishimura <keisuke.nishimura@inria.fr>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] nvme: Add error path for xa_store in nvme_init_effects
Date: Fri, 10 Jan 2025 20:56:34 -0700 [thread overview]
Message-ID: <Z4Hr8lLFENnedjzx@kbusch-mbp> (raw)
In-Reply-To: <20241216152719.17923-1-keisuke.nishimura@inria.fr>
On Mon, Dec 16, 2024 at 04:27:20PM +0100, Keisuke Nishimura wrote:
> The xa_store() may fail due to memory allocation failure because there
> is no guarantee that the index NVME_CSI_NVM is already used. This fix
> introduces a new function to handle the error path.
>
> Fixes: cc115cbe12d9 ("nvme: always initialize known command effects")
> Signed-off-by: Keisuke Nishimura <keisuke.nishimura@inria.fr>
Queued up in nvme-6.14, thanks.
prev parent reply other threads:[~2025-01-11 3:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 15:27 [PATCH v2] nvme: Add error path for xa_store in nvme_init_effects Keisuke Nishimura
2024-12-16 15:49 ` Christoph Hellwig
2025-01-10 9:58 ` Keisuke Nishimura
2025-01-10 22:50 ` Sagi Grimberg
2025-01-11 3:56 ` Keith Busch [this message]
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=Z4Hr8lLFENnedjzx@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keisuke.nishimura@inria.fr \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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