diff options
author | Michal Kubeček <mkubecek@suse.cz> | 2013-08-01 10:04:14 +0200 |
---|---|---|
committer | Ben Hutchings <ben@decadent.org.uk> | 2015-10-13 03:46:13 +0100 |
commit | 2491f0184830c5f1e1c794283177179937def4b7 (patch) | |
tree | 30fae18fdeb7d905106fcacb9271c9a4e11b88ec /mm/migrate.c | |
parent | 4e9592446801b37fc68d8c6a690966c8bd506c40 (diff) | |
download | kernel_samsung_smdk4412-2491f0184830c5f1e1c794283177179937def4b7.zip kernel_samsung_smdk4412-2491f0184830c5f1e1c794283177179937def4b7.tar.gz kernel_samsung_smdk4412-2491f0184830c5f1e1c794283177179937def4b7.tar.bz2 |
ipv6: prevent fib6_run_gc() contention
commit 2ac3ac8f86f2fe065d746d9a9abaca867adec577 upstream.
On a high-traffic router with many processors and many IPv6 dst
entries, soft lockup in fib6_run_gc() can occur when number of
entries reaches gc_thresh.
This happens because fib6_run_gc() uses fib6_gc_lock to allow
only one thread to run the garbage collector but ip6_dst_gc()
doesn't update net->ipv6.ip6_rt_last_gc until fib6_run_gc()
returns. On a system with many entries, this can take some time
so that in the meantime, other threads pass the tests in
ip6_dst_gc() (ip6_rt_last_gc is still not updated) and wait for
the lock. They then have to run the garbage collector one after
another which blocks them for quite long.
Resolve this by replacing special value ~0UL of expire parameter
to fib6_run_gc() by explicit "force" parameter to choose between
spin_lock_bh() and spin_trylock_bh() and call fib6_run_gc() with
force=false if gc_thresh is reached but not max_size.
Signed-off-by: Michal Kubecek <mkubecek@suse.cz>
Signed-off-by: David S. Miller <davem@davemloft.net>
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Cc: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Diffstat (limited to 'mm/migrate.c')
0 files changed, 0 insertions, 0 deletions