From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for 4.20
Date: Fri, 7 Dec 2018 07:38:21 -0800 [thread overview]
Message-ID: <20181207153821.GA14210@infradead.org> (raw)
The following changes since commit ba7aeae5539c7a7cccc4cf07a2bc61281a93c50e:
block, bfq: fix decrement of num_active_groups (2018-12-07 07:40:07 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-4.20
for you to fetch changes up to d7dcdf9d4e15189ecfda24cc87339a3425448d5c:
nvmet-rdma: fix response use after free (2018-12-07 07:11:11 -0800)
----------------------------------------------------------------
Israel Rukshin (1):
nvmet-rdma: fix response use after free
James Smart (1):
nvme: validate controller state before rescheduling keep alive
drivers/nvme/host/core.c | 10 +++++++++-
drivers/nvme/target/rdma.c | 3 ++-
2 files changed, 11 insertions(+), 2 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] nvme fixes for 4.20
Date: Fri, 7 Dec 2018 07:38:21 -0800 [thread overview]
Message-ID: <20181207153821.GA14210@infradead.org> (raw)
The following changes since commit ba7aeae5539c7a7cccc4cf07a2bc61281a93c50e:
block, bfq: fix decrement of num_active_groups (2018-12-07 07:40:07 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-4.20
for you to fetch changes up to d7dcdf9d4e15189ecfda24cc87339a3425448d5c:
nvmet-rdma: fix response use after free (2018-12-07 07:11:11 -0800)
----------------------------------------------------------------
Israel Rukshin (1):
nvmet-rdma: fix response use after free
James Smart (1):
nvme: validate controller state before rescheduling keep alive
drivers/nvme/host/core.c | 10 +++++++++-
drivers/nvme/target/rdma.c | 3 ++-
2 files changed, 11 insertions(+), 2 deletions(-)
next reply other threads:[~2018-12-07 15:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 15:38 Christoph Hellwig [this message]
2018-12-07 15:38 ` [GIT PULL] nvme fixes for 4.20 Christoph Hellwig
2018-12-07 15:40 ` Jens Axboe
2018-12-07 15:40 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2018-11-30 15:24 Christoph Hellwig
2018-11-30 15:24 ` Christoph Hellwig
2018-11-30 15:26 ` Jens Axboe
2018-11-30 15:26 ` Jens Axboe
2018-11-30 15:37 ` Keith Busch
2018-11-30 15:37 ` Keith Busch
2018-11-30 16:26 ` Christoph Hellwig
2018-11-30 16:26 ` Christoph Hellwig
2018-11-30 17:12 ` Jens Axboe
2018-11-30 17:12 ` Jens Axboe
2018-11-09 6:56 Christoph Hellwig
2018-11-09 6:56 ` Christoph Hellwig
2018-11-09 13:16 ` Jens Axboe
2018-11-09 13:16 ` Jens Axboe
2018-11-09 13:20 ` Christoph Hellwig
2018-11-09 13:20 ` Christoph Hellwig
2018-11-09 13:29 ` Jens Axboe
2018-11-09 13:29 ` Jens Axboe
2018-11-09 17:10 ` Sagi Grimberg
2018-11-09 17:10 ` Sagi Grimberg
2018-11-09 17:12 ` Jens Axboe
2018-11-09 17:12 ` Jens Axboe
2018-11-02 6:37 Christoph Hellwig
2018-11-02 6:37 ` Christoph Hellwig
2018-11-02 14:15 ` Jens Axboe
2018-11-02 14:15 ` Jens Axboe
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=20181207153821.GA14210@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--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 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.