All new accounts created on Gitlab now require administrator approval. If you invite any collaborators, please let Flux staff know so they can approve the accounts.

  1. 15 Apr, 2016 4 commits
  2. 11 Apr, 2016 3 commits
  3. 07 Apr, 2016 2 commits
    • Alexander Duyck's avatar
      GRE: Disable segmentation offloads w/ CSUM and we are encapsulated via FOU · a0ca153f
      Alexander Duyck authored
      This patch fixes an issue I found in which we were dropping frames if we
      had enabled checksums on GRE headers that were encapsulated by either FOU
      or GUE.  Without this patch I was barely able to get 1 Gb/s of throughput.
      With this patch applied I am now at least getting around 6 Gb/s.
      The issue is due to the fact that with FOU or GUE applied we do not provide
      a transport offset pointing to the GRE header, nor do we offload it in
      software as the GRE header is completely skipped by GSO and treated like a
      VXLAN or GENEVE type header.  As such we need to prevent the stack from
      generating it and also prevent GRE from generating it via any interface we
      Fixes: c3483384 ("gro: Allow tunnel stacking in the case of FOU/GUE")
      Signed-off-by: default avatarAlexander Duyck <>
      Signed-off-by: default avatarDavid S. Miller <>
    • Stefan Hajnoczi's avatar
      virtio: add VIRTIO_CONFIG_S_NEEDS_RESET device status bit · c00bbcf8
      Stefan Hajnoczi authored
      The VIRTIO 1.0 specification added the DEVICE_NEEDS_RESET device status
      bit in "VIRTIO-98: Add DEVICE_NEEDS_RESET".  This patch defines the
      device status bit in the uapi header file so that both the kernel and
      userspace applications can use it.
      The bit is currently unused by the virtio guest drivers and vhost.
      According to the spec "a good implementation will try to recover by
      issuing a reset".  This is not attempted here because it requires
      auditing the virtio drivers to ensure there are no resource leaks or
      crashes if the device needs to be reset mid-operation.
      See "2.1 Device Status Field" in the VIRTIO 1.0 specification for
      Signed-off-by: default avatarStefan Hajnoczi <>
      Signed-off-by: default avatarMichael S. Tsirkin <>
  4. 06 Apr, 2016 1 commit
  5. 05 Apr, 2016 5 commits
  6. 04 Apr, 2016 5 commits
  7. 01 Apr, 2016 5 commits
    • Lucas Stach's avatar
      mm/page_isolation: fix tracepoint to mirror check function behavior · bbe3de25
      Lucas Stach authored
      Page isolation has not failed if the fin pfn extends beyond the end pfn
      and test_pages_isolated checks this correctly.  Fix the tracepoint to
      report the same result as the actual check function.
      Signed-off-by: default avatarLucas Stach <>
      Acked-by: default avatarVlastimil Babka <>
      Cc: Joonsoo Kim <>
      Signed-off-by: default avatarAndrew Morton <>
      Signed-off-by: default avatarLinus Torvalds <>
    • Chen Gang's avatar
      include/linux/huge_mm.h: return NULL instead of false for pmd_trans_huge_lock() · 969e8d7e
      Chen Gang authored
      The return value of pmd_trans_huge_lock() is a pointer, not a boolean
      value, so use NULL instead of false as the return value.
      Signed-off-by: default avatarChen Gang <>
      Acked-by: default avatarKirill A. Shutemov <>
      Signed-off-by: default avatarAndrew Morton <>
      Signed-off-by: default avatarLinus Torvalds <>
    • Giuseppe CAVALLARO's avatar
      stmmac: fix MDIO settings · a7657f12
      Giuseppe CAVALLARO authored
      Initially the phy_bus_name was added to manipulate the
      driver name but it was recently just used to manage the
      fixed-link and then to take some decision at run-time.
      So the patch uses the is_pseudo_fixed_link and removes
      the phy_bus_name variable not necessary anymore.
      The driver can manage the mdio registration by using phy-handle,
      dwmac-mdio and own parameter e.g. snps,phy-addr.
      This patch takes care about all these possible configurations
      and fixes the mdio registration in case of there is a real
      transceiver or a switch (that needs to be managed by using
      Signed-off-by: default avatarGiuseppe Cavallaro <>
      Reviewed-by: default avatarAndreas Färber <>
      Tested-by: default avatarFrank Schäfer <>
      Cc: Gabriel Fernandez <>
      Cc: Dinh Nguyen <>
      Cc: David S. Miller <>
      Cc: Phil Reid <>
      Signed-off-by: default avatarDavid S. Miller <>
    • Giuseppe CAVALLARO's avatar
      Revert "stmmac: Fix 'eth0: No PHY found' regression" · d7e944c8
      Giuseppe CAVALLARO authored
      This reverts commit 88f8b1bb.
      due to problems on GeekBox and Banana Pi M1 board when
      connected to a real transceiver instead of a switch via
      Signed-off-by: default avatarGiuseppe Cavallaro <>
      Cc: Gabriel Fernandez <>
      Cc: Andreas Färber <>
      Cc: Frank Schäfer <>
      Cc: Dinh Nguyen <>
      Cc: David S. Miller <>
      Signed-off-by: default avatarDavid S. Miller <>
    • Daniel Borkmann's avatar
      tun, bpf: fix suspicious RCU usage in tun_{attach, detach}_filter · 5a5abb1f
      Daniel Borkmann authored
      Sasha Levin reported a suspicious rcu_dereference_protected() warning
      found while fuzzing with trinity that is similar to this one:
        [   52.765684] net/core/filter.c:2262 suspicious rcu_dereference_protected() usage!
        [   52.765688] other info that might help us debug this:
        [   52.765695] rcu_scheduler_active = 1, debug_locks = 1
        [   52.765701] 1 lock held by a.out/1525:
        [   52.765704]  #0:  (rtnl_mutex){+.+.+.}, at: [<ffffffff816a64b7>] rtnl_lock+0x17/0x20
        [   52.765721] stack backtrace:
        [   52.765728] CPU: 1 PID: 1525 Comm: a.out Not tainted 4.5.0+ #264
        [   52.765768] Call Trace:
        [   52.765775]  [<ffffffff813e488d>] dump_stack+0x85/0xc8
        [   52.765784]  [<ffffffff810f2fa5>] lockdep_rcu_suspicious+0xd5/0x110
        [   52.765792]  [<ffffffff816afdc2>] sk_detach_filter+0x82/0x90
        [   52.765801]  [<ffffffffa0883425>] tun_detach_filter+0x35/0x90 [tun]
        [   52.765810]  [<ffffffffa0884ed4>] __tun_chr_ioctl+0x354/0x1130 [tun]
        [   52.765818]  [<ffffffff8136fed0>] ? selinux_file_ioctl+0x130/0x210
        [   52.765827]  [<ffffffffa0885ce3>] tun_chr_ioctl+0x13/0x20 [tun]
        [   52.765834]  [<ffffffff81260ea6>] do_vfs_ioctl+0x96/0x690
        [   52.765843]  [<ffffffff81364af3>] ? security_file_ioctl+0x43/0x60
        [   52.765850]  [<ffffffff81261519>] SyS_ioctl+0x79/0x90
        [   52.765858]  [<ffffffff81003ba2>] do_syscall_64+0x62/0x140
        [   52.765866]  [<ffffffff817d563f>] entry_SYSCALL64_slow_path+0x25/0x25
      Same can be triggered with PROVE_RCU (+ PROVE_RCU_REPEATEDLY) enabled
      from tun_attach_filter() when user space calls ioctl(tun_fd, TUN{ATTACH,
      DETACH}FILTER, ...) for adding/removing a BPF filter on tap devices.
      Since the fix in f91ff5b9 ("net: sk_{detach|attach}_filter() rcu
      fixes") sk_attach_filter()/sk_detach_filter() now dereferences the
      filter with rcu_dereference_protected(), checking whether socket lock
      is held in control path.
      Since its introduction in 99405162 ("tun: socket filter support"),
      tap filters are managed under RTNL lock from __tun_chr_ioctl(). Thus the
      sock_owned_by_user(sk) doesn't apply in this specific case and therefore
      triggers the false positive.
      Extend the BPF API with __sk_attach_filter()/__sk_detach_filter() pair
      that is used by tap filters and pass in lockdep_rtnl_is_held() for the
      rcu_dereference_protected() checks instead.
      Reported-by: default avatarSasha Levin <>
      Signed-off-by: default avatarDaniel Borkmann <>
      Signed-off-by: default avatarDavid S. Miller <>
  8. 31 Mar, 2016 3 commits
  9. 30 Mar, 2016 4 commits
  10. 29 Mar, 2016 4 commits
  11. 28 Mar, 2016 2 commits
    • Dan Williams's avatar
      x86, pmem: use memcpy_mcsafe() for memcpy_from_pmem() · fc0c2028
      Dan Williams authored
      Update the definition of memcpy_from_pmem() to return 0 or a negative
      error code.  Implement x86/arch_memcpy_from_pmem() with memcpy_mcsafe().
      Cc: Borislav Petkov <>
      Cc: Tony Luck <>
      Cc: Thomas Gleixner <>
      Cc: Andy Lutomirski <>
      Cc: Peter Zijlstra <>
      Cc: Andrew Morton <>
      Cc: Linus Torvalds <>
      Acked-by: default avatarIngo Molnar <>
      Reviewed-by: default avatarRoss Zwisler <>
      Signed-off-by: default avatarDan Williams <>
    • Vishwanath Pai's avatar
      netfilter: ipset: fix race condition in ipset save, swap and delete · 596cf3fe
      Vishwanath Pai authored
      This fix adds a new reference counter (ref_netlink) for the struct ip_set.
      The other reference counter (ref) can be swapped out by ip_set_swap and we
      need a separate counter to keep track of references for netlink events
      like dump. Using the same ref counter for dump causes a race condition
      which can be demonstrated by the following script:
      ipset create hash_ip1 hash:ip family inet hashsize 1024 maxelem 500000 \
      ipset create hash_ip2 hash:ip family inet hashsize 300000 maxelem 500000 \
      ipset create hash_ip3 hash:ip family inet hashsize 1024 maxelem 500000 \
      ipset save &
      ipset swap hash_ip3 hash_ip2
      ipset destroy hash_ip3 /* will crash the machine */
      Swap will exchange the values of ref so destroy will see ref = 0 instead of
      ref = 1. With this fix in place swap will not succeed because ipset save
      still has ref_netlink on the set (ip_set_swap doesn't swap ref_netlink).
      Both delete and swap will error out if ref_netlink != 0 on the set.
      Note: The changes to *_head functions is because previously we would
      increment ref whenever we called these functions, we don't do that
      Reviewed-by: default avatarJoshua Hunt <>
      Signed-off-by: default avatarVishwanath Pai <>
      Signed-off-by: default avatarJozsef Kadlecsik <>
      Signed-off-by: default avatarPablo Neira Ayuso <>
  12. 26 Mar, 2016 1 commit
    • Miklos Szeredi's avatar
      fs: add file_dentry() · d101a125
      Miklos Szeredi authored
      This series fixes bugs in nfs and ext4 due to 4bacc9c9 ("overlayfs:
      Make f_path always point to the overlay and f_inode to the underlay").
      Regular files opened on overlayfs will result in the file being opened on
      the underlying filesystem, while f_path points to the overlayfs
      This confuses filesystems which get the dentry from struct file and assume
      it's theirs.
      Add a new helper, file_dentry() [*], to get the filesystem's own dentry
      from the file.  This checks file->f_path.dentry->d_flags against
      DCACHE_OP_REAL, and returns file->f_path.dentry if DCACHE_OP_REAL is not
      set (this is the common, non-overlayfs case).
      In the uncommon case it will call into overlayfs's ->d_real() to get the
      underlying dentry, matching file_inode(file).
      The reason we need to check against the inode is that if the file is copied
      up while being open, d_real() would return the upper dentry, while the open
      file comes from the lower dentry.
      [*] If possible, it's better simply to use file_inode() instead.
      Signed-off-by: default avatarMiklos Szeredi <>
      Signed-off-by: default avatarTheodore Ts'o <>
      Tested-by: default avatarGoldwyn Rodrigues <>
      Reviewed-by: default avatarTrond Myklebust <>
      Cc: <> # v4.2
      Cc: David Howells <>
      Cc: Al Viro <>
      Cc: Daniel Axtens <>
  13. 25 Mar, 2016 1 commit
    • Alexander Potapenko's avatar
      mm, kasan: stackdepot implementation. Enable stackdepot for SLAB · cd11016e
      Alexander Potapenko authored
      Implement the stack depot and provide CONFIG_STACKDEPOT.  Stack depot
      will allow KASAN store allocation/deallocation stack traces for memory
      chunks.  The stack traces are stored in a hash table and referenced by
      handles which reside in the kasan_alloc_meta and kasan_free_meta
      structures in the allocated memory chunks.
      IRQ stack traces are cut below the IRQ entry point to avoid unnecessary
      Right now stackdepot support is only enabled in SLAB allocator.  Once
      KASAN features in SLAB are on par with those in SLUB we can switch SLUB
      to stackdepot as well, thus removing the dependency on SLUB stack
      bookkeeping, which wastes a lot of memory.
      This patch is based on the "mm: kasan: stack depots" patch originally
      prepared by Dmitry Chernenkov.
      Joonsoo has said that he plans to reuse the stackdepot code for the
      mm/page_owner.c debugging facility.
      [ s/depot_stack_handle/depot_stack_handle_t]
      [ comment style fixes]
      Signed-off-by: default avatarAlexander Potapenko <>
      Signed-off-by: default avatarAndrey Ryabinin <>
      Cc: Christoph Lameter <>
      Cc: Pekka Enberg <>
      Cc: David Rientjes <>
      Cc: Joonsoo Kim <>
      Cc: Andrey Konovalov <>
      Cc: Dmitry Vyukov <>
      Cc: Steven Rostedt <>
      Cc: Konstantin Serebryany <>
      Cc: Dmitry Chernenkov <>
      Signed-off-by: default avatarAndrew Morton <>
      Signed-off-by: default avatarLinus Torvalds <>