lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1518474030.3715.167.camel@gmail.com>
Date:   Mon, 12 Feb 2018 14:20:30 -0800
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Yonghong Song <yhs@...com>, ast@...com, daniel@...earbox.net,
        malat@...ian.org, netdev@...r.kernel.org
Cc:     kernel-team@...com
Subject: Re: [PATCH bpf] bpf: fix memory leak in lpm_trie map_free callback
 function

On Mon, 2018-02-12 at 14:15 -0800, Eric Dumazet wrote:
> On Mon, 2018-02-12 at 13:58 -0800, Yonghong Song wrote:
> > There is a memory leak happening in lpm_trie map_free callback
> > function trie_free. The trie structure itself does not get freed.
> > 
> > Also, trie_free function did not do synchronize_rcu before freeing
> > various data structures. This is incorrect as some rcu_read_lock
> > region(s) for lookup, update, delete or get_next_key may not complete yet.
> > The fix is to add synchronize_rcu in the beginning of trie_free.
> > The useless spin_lock is removed from this function as well.
> > 
> > Fixes: b95a5c4db09b ("bpf: add a longest prefix match trie map implementation")
> > Reported-by: Mathieu Malaterre <malat@...ian.org>
> > Reported-by: Alexei Starovoitov <ast@...nel.org>
> > Tested-by: Mathieu Malaterre <malat@...ian.org>
> > Signed-off-by: Yonghong Song <yhs@...com>
> > ---
> >  kernel/bpf/lpm_trie.c | 9 +++++++--
> >  1 file changed, 7 insertions(+), 2 deletions(-)
> > 
> > diff --git a/kernel/bpf/lpm_trie.c b/kernel/bpf/lpm_trie.c
> > index 7b469d1..9b41ea4 100644
> > --- a/kernel/bpf/lpm_trie.c
> > +++ b/kernel/bpf/lpm_trie.c
> > @@ -555,7 +555,12 @@ static void trie_free(struct bpf_map *map)
> >  	struct lpm_trie_node __rcu **slot;
> >  	struct lpm_trie_node *node;
> >  
> > -	raw_spin_lock(&trie->lock);
> > +	/* at this point bpf_prog->aux->refcnt == 0 and this map->refcnt == 0,
> > +	 * so the programs (can be more than one that used this map) were
> > +	 * disconnected from events. Wait for outstanding programs to complete
> > +	 * update/lookup/delete/get_next_key and free the trie.
> > +	 */
> > +	synchronize_rcu();
> >  
> 
> Please do not do that.
> 
> Use kfree_rcu() instead (adding one struct rcu_head in struct lpm_trie)

Oh well, I take this back. It looks we heavily use synchronize_rcu()
all over the places for ->map_free() already.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ