From: Will Deacon <will@kernel.org>
To: David Miller <davem@davemloft.net>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-team@android.com,
g.nault@alphalink.fr
Subject: Re: [PATCH 1/2] l2tp: ensure sessions are freed after their PPPOL2TP socket
Date: Fri, 3 Apr 2020 08:03:02 +0100 [thread overview]
Message-ID: <20200403070301.GA16361@willie-the-truck> (raw)
In-Reply-To: <20200402.125930.1715113142516280666.davem@davemloft.net>
On Thu, Apr 02, 2020 at 12:59:30PM -0700, David Miller wrote:
> Sorry, you will have to repost all of these l2tp patches with proper
> cover letters for a patch series.
>
> In this particular case it's even more necessary, you posted two patch
> series. One with 2 patches and one with 8 patches. Do they depend
> upon eachother? If so, which one goes first. What is each patch
> series doing? How is it doing it? And why are you doing it that way?
>
> Those are the questions answered by a properly written header posting.
Sorry, David. These two series are just backports for stable of patches
that are already in mainline. Git added you to CC because of your SoB
on the patches, but I don't think there's anything for you to do.
The 2-patch series is for 4.9-stable kernels.
The 8-patch series is for 4.4-stable kernels, and it's bigger because
there are missing dependencies in 4.4-stable.
I did call this out in the cover letters but, of course, you weren't CC'd
on those. Duh. Anyway, sorry again for the noise.
Will
next prev parent reply other threads:[~2020-04-03 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 17:31 [PATCH 0/2] [backports] l2tp use-after-free fixes for 4.9 stable Will Deacon
2020-04-02 17:31 ` [PATCH 1/2] l2tp: ensure sessions are freed after their PPPOL2TP socket Will Deacon
2020-04-02 19:59 ` David Miller
2020-04-03 7:03 ` Will Deacon [this message]
2020-04-02 17:31 ` [PATCH 2/2] l2tp: fix race between l2tp_session_delete() and l2tp_tunnel_closeall() Will Deacon
2020-04-02 18:45 ` [PATCH 0/2] [backports] l2tp use-after-free fixes for 4.9 stable 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=20200403070301.GA16361@willie-the-truck \
--to=will@kernel.org \
--cc=davem@davemloft.net \
--cc=g.nault@alphalink.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®