Date: Tue, 19 Sep 2017 18:14:58 +0200
From: Greg KH <greg@kroah.com>
To: Christian Theune <ct@flyingcircus.io>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
        jlayton@poochiereds.net, bfields@fieldses.org
Subject: Re: backport "nfsd: Fix general protection fault in
 release_lock_stateid()" to 4.4
Message-ID: <20170919161458.GA13458@kroah.com>
References: <58785402-6987-416A-9159-739F29CD9923@flyingcircus.io>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <58785402-6987-416A-9159-739F29CD9923@flyingcircus.io>
User-Agent: Mutt/1.9.0 (2017-09-02)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 685
Lines: 11

On Tue, Sep 19, 2017 at 01:16:26PM +0200, Christian Theune wrote:
> Hi,
> 
> I’d like to request inclusion of commit f46c445b79906a9da55c13e0a6f6b6a006b892fe into the 4.4 series. This happens to us regularly on a 4.4.59 machine and a review of the released later changes in 4.4 show that this hasn’t made it into 4.4 yet.
> 
> I’m guessing that using “Option 2” of the stable kernel rules is applicable here as the patch is already accepted in a newer kernel but even when it got the ‘CC: stable@vger.kernel.org” it didn’t trickle down to 4.4.

Oops, my bad for not catching this and getting it merged the first time.
Thanks for the hint, it's now queued up.

greg k-h