Gluon: v2018.2.3 tracking issue

[mweinelt]

Hi, we might need to do another minor release in the v2018.2.x series. There was a regression in the TCP SACK fixes, although I'm not sure if we are affected by it with the services we publicly expose TCP sockets on.

• [x] release notes #1812

• [x] Update past 4.9.184 and 4.14.131 to fix a regression of the TCP SACK fixes that unnecessarily punishes applications with low socket send buffers.

  commit caa51edc7e9606418611e68de624efbd0042adf5
  Author: Eric Dumazet <[email protected]>
  Date:   Fri Jun 21 06:09:55 2019 -0700
  
    tcp: refine memory limit test in tcp_fragment()
  
    commit b6653b3629e5b88202be3c9abc44713973f5c4b4 upstream.
  
    tcp_fragment() might be called for skbs in the write queue.
  
    Memory limits might have been exceeded because tcp_sendmsg() only
    checks limits at full skb (64KB) boundaries.
  
    Therefore, we need to make sure tcp_fragment() wont punish applications
    that might have setup very low SO_SNDBUF values.
  
    Fixes: f070ef2ac667 ("tcp: tcp_fragment() should apply sane memory limits")
    Signed-off-by: Eric Dumazet <[email protected]>
    Reported-by: Christoph Paasch <[email protected]>
    Tested-by: Christoph Paasch <[email protected]>
    Signed-off-by: David S. Miller <[email protected]>
    Signed-off-by: Greg Kroah-Hartman <[email protected]>
  

• [x] fix for passwordless ssh when gluon-authorized-keys was used without gluon-setup-mode
• [x] check for further possible/useful backports from master
• [x] fix for #1790
• [x] 4040 bootloader fix #1766

[rubo77]

The next would be v2018.2.3

[rotanid]

as the OpenWrt 18.06 branch contains the mentioned fixes and a release 18.06.4 has been tagged, we could bump OpenWrt to receive the patch and resolve this issue.
@mweinelt mentioned on IRC though that he is not sure if Gluon is affected by the issue at all.

[rotanid]

the v2018.2.x branch has just been updated with the backports @mweinelt and i decided worth backporting from master branch.

[NeoRaider]

@Adorfer Please open a new ticket with the following info:

• site repo
• build target
• build log

[rotanid]

@Adorfer Please open a new ticket with the following info:

* site repo

* build target

* build log

@Adorfer can you please do this? we don't want releases with new bugs, but we really need more information ...

[rotanid]

i created a PR with a release notes draft: #1812

[rotanid]

closing this as v2018.2.3 has been released.