I consistently receive the following oops on 2.5.72 on an SMP machine after flushing some IPSec policy's and sa's that I had established and sent data through. I have not been able to reproduce this
I consistently receive the following oops on 2.5.72 on an SMP machine after flushing some IPSec policy's and sa's that I had established and sent data through. I've forwarded your report to Herbert,
If your compiler is producing anything like mine, then edi should be smp_processor_id() which looks a bit weird. Please send me your net/core/flow.o file so that I can compare it. What compiler are y
Thanks, you've found two bugs in my code :) Firstly it's only initialising one CPU so only that one has a flow cache. Secondly flow_flush_cache is not checking whether the calling CPU has been initia
Here is the patch. Cheers, -- Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Ke
Here is the patch. Applied, thanks Herbert. Reviewing this made me notice that we don't check the __get_free_pages() return value. I'll fix that. Thanks again.
Thanks. Perhaps we should check that in the init function as well. Cheers, -- Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home P