Francesco Ruggeri <fruggeri@xxxxxxxxxx> wrote: > If a non zero value happens to be in xt[NFPROTO_BRIDGE].cur at > init time, the following panic can be caused by running > % ebtables -t broute -F BROUTING > from a 32-bit user level on a 64-bit kernel. > This patch initializes cur and number fields in xt_init() as in > xt_compat_flush_offsets(). Good catch, thanks for the patch! I think it might be better to switch kmalloc_array to kcalloc instead; this way we don't have to worry about any of these.
