Skip to content
Snippets Groups Projects
  1. Jan 29, 2020
  2. Jan 28, 2020
  3. Jan 26, 2020
  4. Jan 25, 2020
  5. Jan 24, 2020
    • Adrian Schmutzler's avatar
      lantiq: tidy up image/Makefile · 2dc0a8c1
      Adrian Schmutzler authored
      
      This harmonizes indent for Build blocks and removes multiple empty
      lines.
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      2dc0a8c1
    • Adrian Schmutzler's avatar
      lantiq: fix setting SOC to DEFAULT_SOC · 719e1068
      Adrian Schmutzler authored
      
      This adds the missing assignment of DEFAULT_SOC to the SOC variable
      by default.
      
      Fixes: 09ee51c6 ("lantiq: define SOC only once for uniform targets")
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      719e1068
    • Adrian Schmutzler's avatar
      lantiq: define SOC only once for uniform targets · 09ee51c6
      Adrian Schmutzler authored
      
      In lantiq there are several subtarget where all devices have the
      same value set to the SOC variable for each device individually.
      
      This patch introduces a non-device-dependent variable DEFAULT_SOC,
      which is used if no specific SOC is set for a device, and thus reduces
      the number of redundant definitions drastically.
      
      This is applied to all subtargets except xway, as only the latter has
      two different SOCs.
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      09ee51c6
    • Adrian Schmutzler's avatar
      lantiq: move DTS_DIR variable out of Device definition · d9a0794f
      Adrian Schmutzler authored
      
      The DTS_DIR variable is not a device variable, thus it should not
      be set inside Device/Default but globally.
      
      Fixes: c6403709 ("lantiq: use soc_vendor_device scheme on DTS file")
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      d9a0794f
    • Adrian Schmutzler's avatar
      lantiq: fix model name for BT Home Hub 3 Type A · 44cb4fd5
      Adrian Schmutzler authored
      
      The number 3 was accidentally removed from the name during split
      of DEVICE_TITLE.
      
      Fixes: fd666870 ("lantiq: split up DEVICE_TITLE")
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      44cb4fd5
    • Adrian Schmutzler's avatar
      ramips: define SOC only once for uniform targets · dc862be3
      Adrian Schmutzler authored
      
      In ramips, all devices in mt7621, mt76x8 and rt288x subtarget have
      the same value set to the SOC variable for each device individually.
      
      This patch introduces a non-device-dependent variable DEFAULT_SOC,
      which is used if no specific SOC is set for a device, and thus reduces
      the number of redundant definitions drastically.
      
      Signed-off-by: default avatarAdrian Schmutzler <freifunk@adrianschmutzler.de>
      dc862be3
    • Kevin Darbyshire-Bryant's avatar
    • Kevin Darbyshire-Bryant's avatar
    • Koen Vandeputte's avatar
      kernel: bump 4.19 to 4.19.98 · 40842167
      Koen Vandeputte authored
      
      Refreshed all patches.
      
      Compile-tested on: cns3xxx
      Runtime-tested on: cns3xxx
      
      Signed-off-by: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
      40842167
    • Koen Vandeputte's avatar
      kernel: bump 4.14 to 4.14.167 · 76254cb7
      Koen Vandeputte authored
      
      Refreshed all patches.
      
      Compile-tested on: cns3xxx
      Runtime-tested on: cns3xxx
      
      Signed-off-by: default avatarKoen Vandeputte <koen.vandeputte@ncentric.com>
      76254cb7
    • Kevin Darbyshire-Bryant's avatar
      kernel: act_ctinfo: backport memory leak fix · 7a57e82f
      Kevin Darbyshire-Bryant authored
      
      [ Upstream commit 09d4f10a5e78d76a53e3e584f1e6a701b6d24108 ]
      
      Implement a cleanup method to properly free ci->params
      
      BUG: memory leak
      unreferenced object 0xffff88811746e2c0 (size 64):
       comm "syz-executor617", pid 7106, jiffies 4294943055 (age 14.250s)
       hex dump (first 32 bytes):
         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
         c0 34 60 84 ff ff ff ff 00 00 00 00 00 00 00 00  .4`.............
       backtrace:
         [<0000000015aa236f>] kmemleak_alloc_recursive include/linux/kmemleak.h:43 [inline]
         [<0000000015aa236f>] slab_post_alloc_hook mm/slab.h:586 [inline]
         [<0000000015aa236f>] slab_alloc mm/slab.c:3320 [inline]
         [<0000000015aa236f>] kmem_cache_alloc_trace+0x145/0x2c0 mm/slab.c:3549
         [<000000002c946bd1>] kmalloc include/linux/slab.h:556 [inline]
         [<000000002c946bd1>] kzalloc include/linux/slab.h:670 [inline]
         [<000000002c946bd1>] tcf_ctinfo_init+0x21a/0x530 net/sched/act_ctinfo.c:236
         [<0000000086952cca>] tcf_action_init_1+0x400/0x5b0 net/sched/act_api.c:944
         [<000000005ab29bf8>] tcf_action_init+0x135/0x1c0 net/sched/act_api.c:1000
         [<00000000392f56f9>] tcf_action_add+0x9a/0x200 net/sched/act_api.c:1410
         [<0000000088f3c5dd>] tc_ctl_action+0x14d/0x1bb net/sched/act_api.c:1465
         [<000000006b39d986>] rtnetlink_rcv_msg+0x178/0x4b0 net/core/rtnetlink.c:5424
         [<00000000fd6ecace>] netlink_rcv_skb+0x61/0x170 net/netlink/af_netlink.c:2477
         [<0000000047493d02>] rtnetlink_rcv+0x1d/0x30 net/core/rtnetlink.c:5442
         [<00000000bdcf8286>] netlink_unicast_kernel net/netlink/af_netlink.c:1302 [inline]
         [<00000000bdcf8286>] netlink_unicast+0x223/0x310 net/netlink/af_netlink.c:1328
         [<00000000fc5b92d9>] netlink_sendmsg+0x2c0/0x570 net/netlink/af_netlink.c:1917
         [<00000000da84d076>] sock_sendmsg_nosec net/socket.c:639 [inline]
         [<00000000da84d076>] sock_sendmsg+0x54/0x70 net/socket.c:659
         [<0000000042fb2eee>] ____sys_sendmsg+0x2d0/0x300 net/socket.c:2330
         [<000000008f23f67e>] ___sys_sendmsg+0x8a/0xd0 net/socket.c:2384
         [<00000000d838e4f6>] __sys_sendmsg+0x80/0xf0 net/socket.c:2417
         [<00000000289a9cb1>] __do_sys_sendmsg net/socket.c:2426 [inline]
         [<00000000289a9cb1>] __se_sys_sendmsg net/socket.c:2424 [inline]
         [<00000000289a9cb1>] __x64_sys_sendmsg+0x23/0x30 net/socket.c:2424
      
      Fixes: 24ec483cec98 ("net: sched: Introduce act_ctinfo action")
      Signed-off-by: default avatarEric Dumazet <edumazet@google.com>
      Reported-by: default avatarsyzbot <syzkaller@googlegroups.com>
      Cc: Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
      Cc: Cong Wang <xiyou.wangcong@gmail.com>
      Cc: Toke Høiland-Jørgensen <toke@redhat.com>
      Acked-by: default avatarKevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      
      Signed-off-by: default avatarKevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
      7a57e82f
    • Jason A. Donenfeld's avatar
      wireguard-tools: bump to 1.0.20200121 · 4576a753
      Jason A. Donenfeld authored
      
      * Makefile: remove pwd from compile output
      * Makefile: add standard 'all' target
      * Makefile: evaluate git version lazily
      
      Quality of life improvements for packagers.
      
      * ipc: simplify inflatable buffer and add fuzzer
      * fuzz: add generic command argument fuzzer
      * fuzz: add set and setconf fuzzers
      
      More fuzzers and a slicker string list implementation. These fuzzers now find
      themselves configuring wireguard interfaces from scratch after several million
      mutations, which is fun to watch.
      
      * netlink: make sure to clear return value when trying again
      
      Prior, if a dump was interrupted by a concurrent set operation, we'd try
      again, but forget to reset an error flag, so we'd keep trying again forever.
      Now we do the right thing and succeed when we succeed.
      
      * Makefile: sort inputs to linker so that build is reproducible
      
      Earlier versions of make(1) passed GLOB_NOSORT to glob(3), resulting in the
      linker receiving its inputs in a filesystem-dependent order. This screwed up
      reproducible builds.
      
      Signed-off-by: default avatarJason A. Donenfeld <Jason@zx2c4.com>
      4576a753
    • Jason A. Donenfeld's avatar
      wireguard: bump to 0.0.20200121 · ec13b341
      Jason A. Donenfeld authored
      
      * Makefile: strip prefixed v from version.h
      
      This fixes a mistake in dmesg output and when parsing the sysfs entry in the
      filesystem.
      
      * device: skb_list_walk_safe moved upstream
      
      This is a 5.6 change, which we won't support here, but it does make the code
      cleaner, so we make this change to keep things in sync.
      
      * curve25519: x86_64: replace with formally verified implementation
      
      This comes from INRIA's HACL*/Vale. It implements the same algorithm and
      implementation strategy as the code it replaces, only this code has been
      formally verified, sans the base point multiplication, which uses code
      similar to prior, only it uses the formally verified field arithmetic
      alongside reproducable ladder generation steps. This doesn't have a
      pure-bmi2 version, which means haswell no longer benefits, but the
      increased (doubled) code complexity is not worth it for a single
      generation of chips that's already old.
      
      Performance-wise, this is around 1% slower on older microarchitectures,
      and slightly faster on newer microarchitectures, mainly 10nm ones or
      backports of 10nm to 14nm. This implementation is "everest" below:
      
      Xeon E5-2680 v4 (Broadwell)
      
      armfazh: 133340 cycles per call
      everest: 133436 cycles per call
      
      Xeon Gold 5120 (Sky Lake Server)
      
      armfazh: 112636 cycles per call
      everest: 113906 cycles per call
      
      Core i5-6300U (Sky Lake Client)
      
      armfazh: 116810 cycles per call
      everest: 117916 cycles per call
      
      Core i7-7600U (Kaby Lake)
      
      armfazh: 119523 cycles per call
      everest: 119040 cycles per call
      
      Core i7-8750H (Coffee Lake)
      
      armfazh: 113914 cycles per call
      everest: 113650 cycles per call
      
      Core i9-9880H (Coffee Lake Refresh)
      
      armfazh: 112616 cycles per call
      everest: 114082 cycles per call
      
      Core i3-8121U (Cannon Lake)
      
      armfazh: 113202 cycles per call
      everest: 111382 cycles per call
      
      Core i7-8265U (Whiskey Lake)
      
      armfazh: 127307 cycles per call
      everest: 127697 cycles per call
      
      Core i7-8550U (Kaby Lake Refresh)
      
      armfazh: 127522 cycles per call
      everest: 127083 cycles per call
      
      Xeon Platinum 8275CL (Cascade Lake)
      
      armfazh: 114380 cycles per call
      everest: 114656 cycles per call
      
      Achieving these kind of results with formally verified code is quite
      remarkable, especialy considering that performance is favorable for
      newer chips.
      
      Signed-off-by: default avatarJason A. Donenfeld <Jason@zx2c4.com>
      ec13b341
Loading