From: Janne Huttunen <janne.huttunen@nokia.com>
To: <stable@vger.kernel.org>
Subject: Request: d5ce4c31d6df518d for 4.14.y
Date: Tue, 10 Jul 2018 15:14:07 +0300 [thread overview]
Message-ID: <1531224847.29457.12.camel@nokia.com> (raw)
Please consider the two upstream commits below for the 4.14.y
branch.
As a part of an automated test setup, we deploy a disk image into
various types of hardware. With the current 4.14.y kernel and
certain hardware configurations, the first attempt to write the
image to the disk always fails with 'Remote I/O error'. Retrying
the exact same command then always succeeds. The second patch
below fixes this issue allowing the first attempt to work. It
requires the first patch to compile without errors.
commit 425a4dba7953e35ffd096771973add6d2f40d2ed
Author: Ilya Dryomov <idryomov@gmail.com>
Date: Mon Oct 16 15:59:09 2017 +0200
block: factor out __blkdev_issue_zero_pages()
commit d5ce4c31d6df518dd8f63bbae20d7423c5018a6c
Author: Ilya Dryomov <idryomov@gmail.com>
Date: Mon Oct 16 15:59:10 2017 +0200
block: cope with WRITE ZEROES failing in blkdev_issue_zeroout()
next reply other threads:[~2018-07-10 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 12:14 Janne Huttunen [this message]
2018-07-10 13:29 ` Request: d5ce4c31d6df518d for 4.14.y Greg KH
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=1531224847.29457.12.camel@nokia.com \
--to=janne.huttunen@nokia.com \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).