From: Paolo Abeni <pabeni@redhat.com>
To: gregkh@linuxfoundation.org
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
Date: Fri, 23 Feb 2018 09:28:35 +0100 [thread overview]
Message-ID: <1519374515.4161.3.camel@redhat.com> (raw)
In-Reply-To: <1519334010109153@kroah.com>
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 <stable@vger.kernel.org> know about it.
This has 2 required follow-up:
commit dfec091439bb2acf763497cfc58f2bdfc67c56b7
Author: Paolo Abeni <pabeni@redhat.com>
Date: Thu Feb 15 16:59:49 2018 +0100
dn_getsockoptdecnet: move nf_{get/set}sockopt outside sock lock
and:
commit 01ea306f2ac2baff98d472da719193e738759d93
Author: Paolo Abeni <pabeni@redhat.com>
Date: Thu Feb 8 12:19:00 2018 +0100
netfilter: drop outermost socket lock in getsockopt()
I suggest to pull these 3 patches together. My bad: I was unable to
provide a complete fix in a single shot.
Thanks,
Paolo
next prev parent reply other threads:[~2018-02-23 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 21:13 Patch "netfilter: on sockopt() acquire sock lock only in the required scope" has been added to the 4.14-stable tree gregkh
2018-02-23 8:28 ` Paolo Abeni [this message]
2018-02-23 9:01 ` Greg KH
2018-02-23 9:08 ` Paolo Abeni
2018-02-23 9:22 ` Greg KH
2018-02-26 8:32 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1519374515.4161.3.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.