2017-09-19 11:27:33

by Christian Theune

[permalink] [raw]
Subject: backport "nfsd: Fix general protection fault in release_lock_stateid()" to 4.4

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: [email protected] it didn’t trickle down to 4.4.

Kind regards,
Christian

PS: Sorry Jeff, for getting a handful of mails about this as I’m discovering the right way to get this done for the first time. I’ll be happy to pay this debt in beer or other beverages.

--
Christian Theune · [email protected] · +49 345 219401 0
Flying Circus Internet Operations GmbH · http://flyingcircus.io
Forsterstraße 29 · 06112 Halle (Saale) · Deutschland
HR Stendal HRB 21169 · Geschäftsführer: Christian Theune, Christian Zagrodnick


Attachments:
signature.asc (455.00 B)
Message signed with OpenPGP

2017-09-19 17:30:25

by Greg KH

[permalink] [raw]
Subject: Re: backport "nfsd: Fix general protection fault in release_lock_stateid()" to 4.4

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: [email protected] 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

2017-09-19 18:50:31

by Christian Theune

[permalink] [raw]
Subject: Re: backport "nfsd: Fix general protection fault in release_lock_stateid()" to 4.4

Hi,

> On Sep 19, 2017, at 6:14 PM, Greg KH <[email protected]> wrote:
>
> 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: [email protected] 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.

Fantastic, thanks! No expectation about other people being perfect from my point of view as I wouldn’t pass that either. ;)

Hugs,
Christian

--
Christian Theune · [email protected] · +49 345 219401 0
Flying Circus Internet Operations GmbH · http://flyingcircus.io
Forsterstraße 29 · 06112 Halle (Saale) · Deutschland
HR Stendal HRB 21169 · Geschäftsführer: Christian Theune, Christian Zagrodnick


Attachments:
signature.asc (455.00 B)
Message signed with OpenPGP