Re: DEBUG_LOCKS_WARN_ON(in_interrupt()) triggering in socket code

From: Jason A. Donenfeld
Date: Fri Aug 21 2015 - 09:42:43 EST


Ahhh, interesting, so it turns out you can't do a number of things
with a read_lock_bh held, because it increases the softirq count.
Mystery solved.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/