Thread (3 messages) flat view 3 messages, 2 authors, 2007-09-25

Re: [PATCH] Remove broken netfilter binary sysctls from bridging code

From: Patrick McHardy <hidden>
Date: 2007-09-25 04:16:53
Also in: lkml

Stephen Hemminger wrote:
On Mon, 24 Sep 2007 18:55:38 +0200
Patrick McHardy [off-list ref] wrote:
quoted
Eric W. Biederman wrote:
quoted
A really good fix would be to remove the binary side and then to
modify brnf_sysctl_call_tables to allocate a temporary ctl_table and
integer on the stack and only set ctl->data after we have normalized
the written value.  But since in practice nothing cares about
the race a better fix probably isn't worth it.

I seem to be missing something, the entire brnf_sysctl_call_tables
thing looks purely cosmetic to me, wouldn't it be better to simply
remove it?

I agree, removing seems like a better option.  But probably need to go
through a 3-6mo warning period, since sysctl's are technically an API.

I meant removing brnf_sysctl_call_tables function, not the sysctls
themselves, all it does is change values != 0 to 1. Or did you
actually mean that something in userspace might depend on reading
back the value 1 after writing a value != 0?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help