From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@intel.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH] block: pass failfast and driver-specific flags to flush requests
Date: Wed, 6 Jun 2018 16:42:08 +0200 [thread overview]
Message-ID: <20180606144208.GA20487@lst.de> (raw)
In-Reply-To: <20180606142140.64146-1-hare@suse.de>
On Wed, Jun 06, 2018 at 04:21:40PM +0200, Hannes Reinecke wrote:
> If flush requests are being sent to the device we need to inherit the
> failfast and driver-specific flags, too, otherwise I/O will fail.
Looks fine,
Reviewed-by: Christoph Hellwig <hch@lst.de>
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] block: pass failfast and driver-specific flags to flush requests
Date: Wed, 6 Jun 2018 16:42:08 +0200 [thread overview]
Message-ID: <20180606144208.GA20487@lst.de> (raw)
In-Reply-To: <20180606142140.64146-1-hare@suse.de>
On Wed, Jun 06, 2018@04:21:40PM +0200, Hannes Reinecke wrote:
> If flush requests are being sent to the device we need to inherit the
> failfast and driver-specific flags, too, otherwise I/O will fail.
Looks fine,
Reviewed-by: Christoph Hellwig <hch at lst.de>
next prev parent reply other threads:[~2018-06-06 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 14:21 [PATCH] block: pass failfast and driver-specific flags to flush requests Hannes Reinecke
2018-06-06 14:21 ` Hannes Reinecke
2018-06-06 14:28 ` Jens Axboe
2018-06-06 14:28 ` Jens Axboe
2018-06-06 14:42 ` Christoph Hellwig [this message]
2018-06-06 14:42 ` Christoph Hellwig
2018-06-07 8:48 ` Sagi Grimberg
2018-06-07 8:48 ` Sagi Grimberg
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=20180606144208.GA20487@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=hare@suse.com \
--cc=hare@suse.de \
--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.