Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1211187

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

From "Jason A. Donenfeld" <Jason@zx2c4.com>
Newsgroups linux.kernel
Subject Re: DEBUG_LOCKS_WARN_ON(in_interrupt()) triggering in socket code
Date 2015-08-21 15:50 +0200
Message-ID <pZURI-5fy-39@gated-at.bofh.it> (permalink)
References <pZm3E-5ms-7@gated-at.bofh.it> <pZQEq-7Jq-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

DEBUG_LOCKS_WARN_ON(in_interrupt()) triggering in socket code "Jason A. Donenfeld" <Jason@zx2c4.com> - 2015-08-20 02:40 +0200
  Re: DEBUG_LOCKS_WARN_ON(in_interrupt()) triggering in socket code "Jason A. Donenfeld" <Jason@zx2c4.com> - 2015-08-21 11:20 +0200
    Re: DEBUG_LOCKS_WARN_ON(in_interrupt()) triggering in socket code "Jason A. Donenfeld" <Jason@zx2c4.com> - 2015-08-21 15:50 +0200
      Re: DEBUG_LOCKS_WARN_ON(in_interrupt()) triggering in socket code Michal Kubecek <mkubecek@suse.cz> - 2015-08-21 16:10 +0200

csiph-web