From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:48242 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750910AbeBWJBm (ORCPT ); Fri, 23 Feb 2018 04:01:42 -0500 Date: Fri, 23 Feb 2018 10:01:43 +0100 From: Greg KH To: Paolo Abeni Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org Subject: Re: Patch "netfilter: on sockopt() acquire sock lock only in the required scope" has been added to the 4.14-stable tree Message-ID: <20180223090143.GB31038@kroah.com> References: <1519334010109153@kroah.com> <1519374515.4161.3.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519374515.4161.3.camel@redhat.com> Sender: stable-owner@vger.kernel.org List-ID: On Fri, Feb 23, 2018 at 09:28:35AM +0100, Paolo Abeni wrote: > Hi, > > On Thu, 2018-02-22 at 22:13 +0100, gregkh@linuxfoundation.org wrote: > > This is a note to let you know that I've just added the patch titled > > > > netfilter: on sockopt() acquire sock lock only in the required scope > > > > to the 4.14-stable tree which can be found at: > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary > > > > The filename of the patch is: > > netfilter-on-sockopt-acquire-sock-lock-only-in-the-required-scope.patch > > and it can be found in the queue-4.14 subdirectory. > > > > If you, or anyone else, feels it should not be added to the stable tree, > > please let know about it. > > This has 2 required follow-up: > > commit dfec091439bb2acf763497cfc58f2bdfc67c56b7 > Author: Paolo Abeni > Date: Thu Feb 15 16:59:49 2018 +0100 > > dn_getsockoptdecnet: move nf_{get/set}sockopt outside sock lock Now applied, thanks. > and: > > commit 01ea306f2ac2baff98d472da719193e738759d93 > Author: Paolo Abeni > Date: Thu Feb 8 12:19:00 2018 +0100 > > netfilter: drop outermost socket lock in getsockopt() This one isn't in Linus's tree yet. What tree is it in right now? > I suggest to pull these 3 patches together. My bad: I was unable to > provide a complete fix in a single shot. Not a problem, many thanks for letting me know. greg k-h