Comment 5 for bug 1672470

With a virsh guest installed with standard xenial, using the 4.4.0-72-generic kernel, I created a bridge and attached the virtio interface to it. I then started iperf3 -s on the guest, and started iperf3 -c GUESTIP -t 300 on the host, to create continuous traffic to the guest.

Then I added a simple iptables rule:
$ sudo iptables -A INPUT -s 192.168.122.0/24 -j MARK --set-mark 1234

that rule matches all incoming iperf3 packets. Then, simply modprobing the br_netfilter module reproduces this kernel oops.

I then added xenial-proposed to the apt sources, and upgraded the kernel to version 4.4.0-74-generic, and re-ran the above test, which allowed the br_netfilter module to be loaded with no kernel oops or other problem.