From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: eric.dumazet@gmail.com, Valdis.Kletnieks@vt.edu,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: zillions of lockdep whinges in include/net/sock.h:1408
Date: Sun, 24 Apr 2016 14:54:21 -0400 (EDT) [thread overview]
Message-ID: <20160424.145421.128023840849290353.davem@davemloft.net> (raw)
In-Reply-To: <571D14F8.6070306@stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Sun, 24 Apr 2016 20:48:24 +0200
> Eric's patch is worth to apply anyway, but I am not sure if it solves
> the (fundamental) problem. I couldn't reproduce it with the exact next-
> tag provided in the initial mail. All other reports also only happend
> with linux-next and not net-next.
Ok, Eric please submit it formally.
Thanks!
next prev parent reply other threads:[~2016-04-24 18:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 0:30 linux-next: zillions of lockdep whinges in include/net/sock.h:1408 Valdis Kletnieks
2016-04-21 7:42 ` Hannes Frederic Sowa
2016-04-21 9:05 ` Valdis.Kletnieks
2016-04-21 13:31 ` Eric Dumazet
2016-04-21 13:49 ` Hannes Frederic Sowa
2016-04-24 18:38 ` David Miller
2016-04-24 18:48 ` Hannes Frederic Sowa
2016-04-24 18:54 ` David Miller [this message]
2016-04-24 19:55 ` Eric Dumazet
2016-04-24 19:46 ` Eric Dumazet
2016-04-24 19:56 ` Valdis.Kletnieks
2016-04-24 21:00 ` Eric Dumazet
2016-04-24 21:13 ` Valdis.Kletnieks
2016-04-24 21:25 ` Eric Dumazet
2016-04-24 21:28 ` Eric Dumazet
2016-04-25 13:26 ` Hannes Frederic Sowa
2016-04-25 13:34 ` [PATCH v2 net-next] sock: relax WARN_ON() in sock_owned_by_user() Eric Dumazet
2016-04-25 15:50 ` David Miller
2016-04-21 18:10 ` linux-next: zillions of lockdep whinges in include/net/sock.h:1408 Hannes Frederic Sowa
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=20160424.145421.128023840849290353.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=eric.dumazet@gmail.com \
--cc=hannes@stressinduktion.org \
--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;
as well as URLs for NNTP newsgroup(s).