bridge-timer-fix.patch for F19

[Josh Boyer]

On Mon, Jul 08, 2013 at 10:05:55AM +0200, poma wrote:
> On 07.07.2013 15:21, poma wrote:
> > On 06.07.2013 14:16, Josh Boyer wrote:
> >> On Sat, Jul 6, 2013 at 2:05 AM, poma <pomidorabelisima at gmail.com> wrote:
> >>>
> >>> Please don't forget us at Schrödinger’s Caffè.
> >>> F17 & F18 already have it.
> >>
> >> It's already committed in the F19 branch.
> >>
> >> josh
> >>
> > 
> > OK, thanks.
> > These are some data regarding.
> > 
> > Results of testing the system stability due to domain reset
> > - KVM & virtio_net
> > 
> > Recompiled & patched - kernel-3.9.9-302.fc19.src.rpm:
> > - kernel-3.9.9-502.fc19.x86_64 - PASSED/RUNNING
> >   bridge-timer-fix-complete.patch(br_multicast.c & br_mdb.c) [1]
> > 
> > Recompiled & patched - kernel-3.10.0-1.fc20.src.rpm:
> > - kernel-3.10.0-303.fc19.x86_64 - FAILED/FREEZE
> >   bridge-timer-fix.patch(br_multicast.c)
> > - kernel-3.10.0-505.fc19.x86_64 - FAILED/FREEZE
> >   bridge-timer-fix-complete.patch(br_multicast.c & br_mdb.c) [1]
> …
> > [1]
> > http://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1
> 
> To conclude,
> 
> Built with config-3.10.0-505.fc19.x86_64
> - net-next kernel-3.10.0-net-next.fc19.x86_64 - FAILED/FREEZE
>   net-next.git commit c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1(last) [1]

I believe both your 3.10.0-303 and 3.10.0-505 commits are missing a
use-after-free fix in the vhost-net driver.  The fixed upstream version
was sent yesterday and still isn't applied to any tree that I can see.

josh