From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from out1-smtp.messagingengine.com ([66.111.4.25]:52043 "EHLO
        out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S933138AbeGJN3z (ORCPT
        <rfc822;stable@vger.kernel.org>); Tue, 10 Jul 2018 09:29:55 -0400
Date: Tue, 10 Jul 2018 15:29:53 +0200
From: Greg KH <greg@kroah.com>
To: Janne Huttunen <janne.huttunen@nokia.com>
Cc: stable@vger.kernel.org
Subject: Re: Request: d5ce4c31d6df518d for 4.14.y
Message-ID: <20180710132953.GA19794@kroah.com>
References: <1531224847.29457.12.camel@nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1531224847.29457.12.camel@nokia.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Tue, Jul 10, 2018 at 03:14:07PM +0300, Janne Huttunen wrote:
> 
> 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()� ��

Now queued up, thanks.