summaryrefslogtreecommitdiff
path: root/target/linux/generic/backport-4.9/070-bcma-from-4.11.patch
diff options
context:
space:
mode:
authorKevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>2018-06-18 09:08:05 +0000
committerJohn Crispin <john@phrozen.org>2018-06-18 21:29:34 +0200
commit8af649756f92d956a4c418bbd1817954cffa4ef5 (patch)
treebc0f4ca8c33db6fdda85e2a4012a93e6b874a90a /target/linux/generic/backport-4.9/070-bcma-from-4.11.patch
parentb6c134f254fcc60d0474e037af5e62c94931d743 (diff)
downloadmtk-20170518-8af649756f92d956a4c418bbd1817954cffa4ef5.zip
mtk-20170518-8af649756f92d956a4c418bbd1817954cffa4ef5.tar.gz
mtk-20170518-8af649756f92d956a4c418bbd1817954cffa4ef5.tar.bz2
kernel: atm: pppoatm fix vc-mux connection failures
Backport a hot off the press upstream kernel ATM fix: Preserve value of skb->truesize when accounting to vcc "There's a hack in pskb_expand_head() to avoid adjusting skb->truesize for certain skbs. Ideally it would cover ATM too. It doesn't. Just stashing the accounted value and using it in atm_raw_pop() is probably the easiest way to cope." The issue was exposed by upstream with: commit 14afee4b6092fde451ee17604e5f5c89da33e71e Author: Reshetova, Elena <elena.reshetova@intel.com> Date: Fri Jun 30 13:08:00 2017 +0300 net: convert sock.sk_wmem_alloc from atomic_t to refcount_t But an earlier commit left the ticking timebomb: 158f323b9868 ("net: adjust skb->truesize in pskb_expand_head() Sincerest thanks to Mathias Kresin <dev@kresin.me> for debugging assistance and to David Woodhouse <dwmw2@infradead.org> for further guidance, cajoling & patience in interpreting the debug I was giving him and producing a fix! Fixes FS#1567 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> (cherry picked from commit d600de3ddde269bf0b324735f8f12278f82d9b37)
Diffstat (limited to 'target/linux/generic/backport-4.9/070-bcma-from-4.11.patch')
0 files changed, 0 insertions, 0 deletions