All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stefan Schmidt <stefan@osg.samsung.com>
Cc: stable@vger.kernel.org, Alexander Aring <aring@mojatatu.com>,
	"David S. Miller" <davem@davemloft.net>,
	"linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>
Subject: Re: net: ieee802154: 6lowpan: fix frag reassembly
Date: Thu, 17 May 2018 10:59:19 +0200	[thread overview]
Message-ID: <20180517085919.GD25318@kroah.com> (raw)
In-Reply-To: <142208d4-6ca6-5923-327c-8d1cb069ceb8@osg.samsung.com>

On Mon, May 14, 2018 at 05:22:18PM +0200, Stefan Schmidt wrote:
> Hello.
> 
> 
> Please apply f18fa5de5ba7f1d6650951502bb96a6e4715a948
> 
> (net: ieee802154: 6lowpan: fix frag reassembly) to the 4.16.x stable tree.
> 
> 
> Earlier trees are not needed as the problem was introduced in 4.16.

Really?  Commit f18fa5de5ba7 ("net: ieee802154: 6lowpan: fix frag
reassembly") says it fixes commit 648700f76b03 ("inet: frags: use
rhashtables for reassembly units") which did not show up until 4.17-rc1:
	$ git describe --contains 648700f76b03
	v4.17-rc1~148^2~20^2~11

Also, it did not get backported to 4.16.y, so I don't see how it is
needed in 4.16-stable.

To verify this, I tried applying the patch, and it totally fails to
apply to the 4.16.y tree.

So are you _sure_ you want/need this in 4.16?  If so, can you provide a
working backport that you have verified works?

thanks,

greg k-h

  parent reply	other threads:[~2018-05-17  8:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 15:22 net: ieee802154: 6lowpan: fix frag reassembly Stefan Schmidt
2018-05-14 15:31 ` Greg KH
2018-05-14 16:13 ` David Miller
2018-05-17  8:59 ` Greg KH [this message]
2018-05-17 14:16   ` Stefan Schmidt
2018-05-17 15:59     ` 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=20180517085919.GD25318@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aring@mojatatu.com \
    --cc=davem@davemloft.net \
    --cc=linux-wpan@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stefan@osg.samsung.com \
    /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.