Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 5 Aug 2020 16:29:46 +0200
From:   Greg KH <greg@kroah.com>
To:     Jan Kara <jack@suse.cz>
Cc:     stable@vger.kernel.org, tytso@mit.edu, adilger.kernel@dilger.ca,
        linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
        wanglong19@meituan.com, heguanjun@meituan.com,
        Jiang Ying <jiangying8582@126.com>
Subject: Re: [PATCH v4] ext4: fix direct I/O read error
Message-ID: <20200805142946.GA2154236@kroah.com>
References: <1596614241-178185-1-git-send-email-jiangying8582@126.com>
 <20200805085107.GC4117@quack2.suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200805085107.GC4117@quack2.suse.cz>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Aug 05, 2020 at 10:51:07AM +0200, Jan Kara wrote:
> Note to stable tree maintainers (summary from the rather long changelog):
> This is a non-upstream patch. It will not go upstream because the problem
> there has been fixed by converting ext4 to use iomap infrastructure.
> However that change is out of scope for stable kernels and this is a
> minimal fix for the problem that has hit real-world applications so I think
> it would be worth it to include the fix in stable trees. Thanks.

Thanks for the note, I wouldn't have noticed it otherwise :)

greg k-h