Re: [PATCH nf-next v3 1/2] netfilter: Fix potential null pointer dereference

Eric Dumazet writes: > On Wed, 2016-09-28 at 10:56 -0400, Aaron Conole wrote: >> Eric Dumazet writes: >> >> > On Wed, 2016-09-28 at 09:12 -0400, Aaron Conole wrote: >> >> It's possible for nf_hook_entry_head to return NULL. If two >> >>

Re: [PATCH nf-next v3 1/2] netfilter: Fix potential null pointer dereference

On Wed, 2016-09-28 at 10:56 -0400, Aaron Conole wrote: > Eric Dumazet writes: > > > On Wed, 2016-09-28 at 09:12 -0400, Aaron Conole wrote: > >> It's possible for nf_hook_entry_head to return NULL. If two > >> nf_unregister_net_hook calls happen simultaneously with a

Re: [PATCH nf-next v3 1/2] netfilter: Fix potential null pointer dereference

Eric Dumazet writes: > On Wed, 2016-09-28 at 09:12 -0400, Aaron Conole wrote: >> It's possible for nf_hook_entry_head to return NULL. If two >> nf_unregister_net_hook calls happen simultaneously with a single hook >> entry in the list, both will enter the nf_hook_mutex

Re: [PATCH nf-next v3 1/2] netfilter: Fix potential null pointer dereference

On Wed, 2016-09-28 at 09:12 -0400, Aaron Conole wrote: > It's possible for nf_hook_entry_head to return NULL. If two > nf_unregister_net_hook calls happen simultaneously with a single hook > entry in the list, both will enter the nf_hook_mutex critical section. > The first will successfully

[PATCH nf-next v3 1/2] netfilter: Fix potential null pointer dereference

It's possible for nf_hook_entry_head to return NULL. If two nf_unregister_net_hook calls happen simultaneously with a single hook entry in the list, both will enter the nf_hook_mutex critical section. The first will successfully delete the head, but the second will see this NULL pointer and