> The change that triggered these probs is that
> spin_lock_irq(&lock) on UP mapped
> previously --> cli();
> now --> local_irq_disable();spin_lock(&lock);
> +--> (void)(&lock);
> ie. "lock" must exist.
Yup, s'what I said (though I wasn't necessarily clear enough) :)
> And YES, in UP that cli() (or equiv.) MUST exist (masq_port variable IS
> changed from U-space [ip_masq_user module] and obviously from kernel [bh]).
How come? As I understand it,
the masq stuff is called by the networking stuff
the networking stuff is called from the bottom half
the bottom halves are run in sched.c, out of irq context (obviously)
-- Plug-and-Play is really nice, unfortunately it only works 50% of the time. To be specific the "Plug" almost always works. --unknown source- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/