From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] block: Initialize max_dev_sectors to 0
Date: Wed, 2 Mar 2016 22:42:17 +0000 [thread overview]
Message-ID: <20160302224216.GF27636@localhost.localdomain> (raw)
In-Reply-To: <20160301151951.GA21997@infradead.org>
On Tue, Mar 01, 2016@07:19:51AM -0800, Christoph Hellwig wrote:
> Btw, I think we also needs this for 4.4-stable, especially as it's
> going to be a long term release.
Agreed, I even received bug reports this week for this issue from
folks using 4.4-stable at the NVMe plugfest. I posted this patch to the
stable list.
prev parent reply other threads:[~2016-03-02 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 23:52 [PATCH] block: Initialize max_dev_sectors to 0 Keith Busch
2016-02-11 13:01 ` Sagi Grimberg
2016-02-11 15:20 ` Christoph Hellwig
2016-02-11 15:21 ` Jens Axboe
2016-03-01 15:19 ` Christoph Hellwig
2016-03-02 22:42 ` 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=20160302224216.GF27636@localhost.localdomain \
--to=keith.busch@intel.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