Hello! > > if [ "$CONFIG_SMP" = "n" ]; then > > bool 'Preemptible Kernel' CONFIG_PREEMPT > > fi > > > That is not a fix! It is dodging the issue. ;) It is the only real fix, if you are going to follow this instruction: +RULE #1: Per-CPU data structures need explicit protection + + +Two similar problems arise. An example code snippet: + + struct this_needs_locking tux[NR_CPUS]; + tux[smp_processor_id()] = some_value; + /* task is preempted here... */ + something = tux[smp_processor_id()]; + +First, since the data is per-CPU, it may not have explicit SMP locking, but +require it otherwise. Second, when a preempted task is finally rescheduled, +the previous value of smp_processor_id may not equal the current. You must +protect these situations by disabling preemption around them. If you are not going to break all the kernel just make sure that tasks preempted in the kernel do not migrate. That's all, simple & stupid. Alexey - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
