Re: [PATCH AUTOSEL for 4.14 057/100] nfsd: Ensure we don't recognise lock stateids after freeing them

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH AUTOSEL for 4.14 057/100] nfsd: Ensure we don't recognise lock stateids after freeing them
From: Sasha Levin <Alexander.Levin@xxxxxxxxxxxxx>
Date: Wed, 24 Jan 2018 17:28:02 +0000
Accept-language: en-US
Cc: "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "stable@xxxxxxxxxxxxxxx" <stable@xxxxxxxxxxxxxxx>, Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx>
In-reply-to: <20180124154709.GB31619@parsley.fieldses.org>
Spamdiagnosticmetadata: NSPM
Spamdiagnosticoutput: 1:99
Thread-index: AQHTlMni0FqA8X0CD0ukthGE9IUuU6ODK5uAgAAcL4A=
Thread-topic: [PATCH AUTOSEL for 4.14 057/100] nfsd: Ensure we don't recognise lock stateids after freeing them

On Wed, Jan 24, 2018 at 10:47:09AM -0500, J. Bruce Fields wrote:
>Chuck Lever found this caused a regression, and Trond's fix hasn't hit
>Linus's tree yet.

I'll remove it from all trees for now, thanks!

--
Thanks,
Sasha

References:
- [PATCH AUTOSEL for 4.14 001/100] drm/vc4: Account for interrupts in flight
  - From: Sasha Levin
- [PATCH AUTOSEL for 4.14 057/100] nfsd: Ensure we don't recognise lock stateids after freeing them
  - From: Sasha Levin
- Re: [PATCH AUTOSEL for 4.14 057/100] nfsd: Ensure we don't recognise lock stateids after freeing them
  - From: J. Bruce Fields

Prev by Date: Re: [PATCH AUTOSEL for 4.9 38/55] fs/mbcache.c: make count_objects() more robust
Next by Date: Re: [PATCH] lib/strscpy: remove word-at-a-time optimization.
Previous by thread: Re: [PATCH AUTOSEL for 4.14 057/100] nfsd: Ensure we don't recognise lock stateids after freeing them
Next by thread: [PATCH AUTOSEL for 4.14 063/100] hwmon: (pmbus) Use 64bit math for DIRECT format values
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel] [Kernel Development Newbies] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite Hiking] [Linux Kernel] [Linux SCSI]