mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: 허종만 <jongman.heo@samsung.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 3.13.0-rc1+ INFO: inconsistent lock state
Date: Thu, 28 Nov 2013 08:18:06 +0100	[thread overview]
Message-ID: <20131128071806.GE20630@order.stressinduktion.org> (raw)
In-Reply-To: <13025162.118881385612276530.JavaMail.weblogic@epv6ml01>

On Thu, Nov 28, 2013 at 04:17:56AM +0000, 허종만 wrote:
> With current linus git (HEAD 8ae516aa), I got following kernel message.
> This is slightly different from what I had reported recently (14th Nov).

I guess the prolem is that the STATS _BH functions are to be used if they
are executed in bottom half and maybe people expect it to protect against
bottom half. We seem to have some more of this problems in udp_sendmsg
(this trace) and ping_sendmsg, maybe in tcp, too. The non-_BH functions
actually disable bh.

I'll check for more prolems and will post a patch.

Thanks for reporting,

  Hannes


  reply	other threads:[~2013-11-28  7:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28  4:17 허종만
2013-11-28  7:18 ` Hannes Frederic Sowa [this message]
2013-11-28 17:23 ` [PATCH] udp: fix possible seqlock deadlock Eric Dumazet
2013-11-28 17:36   ` Eric Dumazet
2013-11-28 17:51   ` [PATCH v2] inet: fix possible seqlock deadlocks Eric Dumazet
2013-11-28 18:09     ` Hannes Frederic Sowa
2013-11-29 21:38       ` David Miller
2013-11-28 19:22     ` [PATCH] inet: further fixes of " Hannes Frederic Sowa
2013-11-28 21:01       ` Eric Dumazet
2013-11-28 21:27         ` Hannes Frederic Sowa
2013-11-28 22:19           ` Hannes Frederic Sowa
2013-11-28 23:15             ` David Miller
2013-11-29  5:39       ` [PATCH] ipv6: fix possible seqlock deadlock in ip6_finish_output2 Hannes Frederic Sowa
2013-11-30 16:45         ` Eric Dumazet
2013-11-30 17:49           ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131128071806.GE20630@order.stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=jongman.heo@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome