From: hch@lst.de (Christoph Hellwig)
Subject: [GIT PULL] nvme fix for 4.16-rc6
Date: Fri, 16 Mar 2018 17:16:55 +0100 [thread overview]
Message-ID: <20180316161655.GA13293@lst.de> (raw)
In-Reply-To: <e58b5357-6885-75dc-c027-9bea3cd6829d@kernel.dk>
On Fri, Mar 16, 2018@09:14:34AM -0700, Jens Axboe wrote:
> On 3/16/18 9:01 AM, Keith Busch wrote:
> > Hi Jens,
> >
> > One last fix from Jianchao to address a troubling scenario Ming identified
> > with offlining CPUs that could leave nvme controllers unusable. We can
> > not allow that to occur, so we wish to include a new IRQ spread that
> > prevents that situation.
>
> Since this isn't really a regression in this release, how about
> we push this one to 4.17 instead?
It is a regression in 4.15. So I think we should fix this ASAP.
next prev parent reply other threads:[~2018-03-16 16:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 16:01 [GIT PULL] nvme fix for 4.16-rc6 Keith Busch
2018-03-16 16:14 ` Jens Axboe
2018-03-16 16:16 ` Christoph Hellwig [this message]
2018-03-16 16:26 ` Jens Axboe
2018-03-16 16:53 ` Keith Busch
2018-03-21 20:59 ` Keith Busch
2018-03-21 21:02 ` Jens Axboe
2018-03-21 21:44 ` Jens Axboe
2018-03-21 22:08 ` Keith Busch
2018-03-22 21:09 ` Keith Busch
2018-03-22 21:32 ` Jens Axboe
2018-03-22 22:02 ` Keith Busch
2018-03-22 22:09 ` 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=20180316161655.GA13293@lst.de \
--to=hch@lst.de \
/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