From: David S. Miller Date: Tue, 4 Jul 2017 08:29:05 +0000 (-0700) Subject: Merge branch 'ipv4-ipv6-refcount_t' X-Git-Tag: v4.13~415^2~13 X-Git-Url: https://git.proxmox.com/?a=commitdiff_plain;h=2671e9fc62c392abea6a5e80297dfb03fdbae2e7;p=mirror_ubuntu-artful-kernel.git Merge branch 'ipv4-ipv6-refcount_t' Elena Reshetova says: ==================== v2 ipv4/ipv6 refcount conversions Changes in v2: * rebase on top of net-next * currently by default refcount_t = atomic_t (*) and uses all atomic standard operations unless CONFIG_REFCOUNT_FULL is enabled. This is a compromise for the systems that are critical on performance (such as net) and cannot accept even slight delay on the refcounter operations. This series, for ipv4/ipv6 network components, replaces atomic_t reference counters with the new refcount_t type and API (see include/linux/refcount.h). By doing this we prevent intentional or accidental underflows or overflows that can led to use-after-free vulnerabilities. The patches are fully independent and can be cherry-picked separately. In order to try with refcount functionality enabled in run-time, CONFIG_REFCOUNT_FULL must be enabled. NOTE: automatic kernel builder for some reason doesn't like all my network branches and regularly times out the builds on these branches. Suggestion for "waiting a day for a good coverage" doesn't work, as we have seen with generic network conversions. So please wait for the full report from kernel test rebot before merging further up. This has been compile-tested in 116 configs, but 71 timed out (including all s390-related configs again). I am trying to see if they can fix build coverage for me in meanwhile. * The respective change is currently merged into -next as "locking/refcount: Create unchecked atomic_t implementation". ==================== Signed-off-by: David S. Miller --- 2671e9fc62c392abea6a5e80297dfb03fdbae2e7