Bug#668511: Kernel panic with bridge networking

[Jonathan Nieder <jrnieder@gmail.com>]

# patch applied to mainline
tags 668511 - moreinfo
quit

Hi Max,

Massimo Cetra wrote:

> It didn't work the way it was described in that document. Probably
> because i'm on squeeze and test-patch throw some python exceptions
> that do not happen on wheezy.
>
> Instead:
> - i downloaded the debian sourrces with dget.
> - i applied the patch manually (it's very short) because the offsets
> were not the same
> - i re-generated the sources with dpkg-buildpackage -S
> - i boult the whole linux-$stuff with pbuilder.

Sounds painful.  Here are instructions for testing against upstream
source, which might be easier.

 0. prerequisites

	apt-get install git build-essential

 1. get the kernel history, if you don't already have it

	git clone \
	  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

 2. fetch point releases

	cd linux
	git remote add stable \
	  git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
	git fetch stable

 3. configure, build, test

	git checkout stable/linux-3.2.y
	cp /boot/config-$(uname -r) .config; # current configuration
	scripts/config --disable DEBUG_INFO
	make localmodconfig; # optional: minimize configuration
	make deb-pkg; # optionally with -j<num> for parallel build
	dpkg -i ../<name of package>
	reboot

    Hopefully it reproduces the bug.  So:

 4. try the patch

	cd linux
	git cherry-pick -x -s a881e963c7fe
	make deb-pkg; # maybe with -j4
	dpkg -i ../<name of package>
	reboot

You wrote at [1] that this doesn't seem to have completely solved the
bridging-related panics.  Am I correct in assuming the patch still
works as advertised, though?  Are there other patches we should pick
up?

Hope that helps,
Jonathan

[1] http://thread.gmane.org/gmane.linux.kernel/1283112/focus=227842