From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:54468 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750727AbdKFInl (ORCPT
        <rfc822;stable@vger.kernel.org>); Mon, 6 Nov 2017 03:43:41 -0500
Date: Mon, 6 Nov 2017 09:43:53 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: stable@vger.kernel.org
Subject: Re: Please backport: vfs: deny copy_file_range() for non regular
 files
Message-ID: <20171106084353.GB8571@kroah.com>
References: <20171008011933.yvkrl35hk2q2xrmp@thunk.org>
 <20171010180607.GF747@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171010180607.GF747@kroah.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Tue, Oct 10, 2017 at 08:06:07PM +0200, Greg KH wrote:
> On Sat, Oct 07, 2017 at 09:19:33PM -0400, Theodore Ts'o wrote:
> > Hi, please cherry pick the following upstream commit:
> > 
> >    11cbfb10775a: vfs: deny copy_file_range() for non regular files
> > 
> > to 3.18, 4.1, 4.4, and 4.9 LTS stable kernels.
> 
> It does not apply to the 3.18 or 4.4 stable kernels.  It worked for 4.9.
> Don't care about 4.1 :)
> 
> Do you have a working backport anywhere?

To follow up with this, copy_file_ranges() showed up in the 4.5 kernel
release, so how is this a problem for older kernels than that?

thanks,

greg k-h