From: Christoph Hellwig <hch@lst.de>
To: Niklas Cassel <niklas.cassel@wdc.com>
Cc: "Jens Axboe" <axboe@kernel.dk>,
"Sagi Grimberg" <sagi@grimberg.me>,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
"Jens Axboe" <axboe@fb.com>,
"Javier González" <javier@cnexlabs.com>,
"Keith Busch" <kbusch@kernel.org>,
"Matias Bjørling" <mb@lightnvm.io>,
"Christoph Hellwig" <hch@lst.de>,
"Igor Konopko" <igor.j.konopko@intel.com>
Subject: Re: [PATCH] nvme: prevent double free in nvme_alloc_ns() error handling
Date: Mon, 27 Apr 2020 17:06:12 +0200 [thread overview]
Message-ID: <20200427150612.GA5910@lst.de> (raw)
In-Reply-To: <20200427123443.520469-1-niklas.cassel@wdc.com>
Applied to nvme-5.7.
Not a huge fan of it, though - but I think I have an idea how to sort
some of this mess out with better block layer APIs.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Niklas Cassel <niklas.cassel@wdc.com>
Cc: "Keith Busch" <kbusch@kernel.org>, "Jens Axboe" <axboe@fb.com>,
"Christoph Hellwig" <hch@lst.de>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Igor Konopko" <igor.j.konopko@intel.com>,
"Matias Bjørling" <mb@lightnvm.io>,
"Javier González" <javier@cnexlabs.com>,
"Jens Axboe" <axboe@kernel.dk>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme: prevent double free in nvme_alloc_ns() error handling
Date: Mon, 27 Apr 2020 17:06:12 +0200 [thread overview]
Message-ID: <20200427150612.GA5910@lst.de> (raw)
In-Reply-To: <20200427123443.520469-1-niklas.cassel@wdc.com>
Applied to nvme-5.7.
Not a huge fan of it, though - but I think I have an idea how to sort
some of this mess out with better block layer APIs.
next prev parent reply other threads:[~2020-04-27 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 12:34 [PATCH] nvme: prevent double free in nvme_alloc_ns() error handling Niklas Cassel
2020-04-27 12:34 ` Niklas Cassel
2020-04-27 15:06 ` Christoph Hellwig [this message]
2020-04-27 15:06 ` Christoph Hellwig
2020-04-27 18:03 ` Javier González
2020-04-27 18:03 ` Javier González
2020-04-27 18:22 ` Niklas Cassel
2020-04-27 18:22 ` Niklas Cassel
2020-04-28 7:06 ` Javier González
2020-04-28 7:06 ` Javier González
2020-04-28 7:49 ` Niklas Cassel
2020-04-28 7:49 ` Niklas Cassel
2020-04-28 10:32 ` Javier González
2020-04-28 10:32 ` Javier González
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=20200427150612.GA5910@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=igor.j.konopko@intel.com \
--cc=javier@cnexlabs.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mb@lightnvm.io \
--cc=niklas.cassel@wdc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.