All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>, Thomas Graf <tgraf@suug.ch>,
	netdev <netdev@vger.kernel.org>
Subject: Re: netlink & rhashtable status
Date: Wed, 13 May 2015 21:38:41 -0700	[thread overview]
Message-ID: <1431578321.27831.43.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <20150514042151.GA5482@gondor.apana.org.au>

On Thu, 2015-05-14 at 12:21 +0800, Herbert Xu wrote:
> On Thu, May 14, 2015 at 12:16:28PM +0800, Herbert Xu wrote:
> > On Wed, May 13, 2015 at 09:13:38PM -0700, Eric Dumazet wrote:
> > >
> > > So it looks like we lost an skb or something....
> > 
> > OK that sounds reasonable.  So my plan is to disable dynamic
> > rehashing and then hunt down this lookup bug.
> 
> Oh wait this isn't even a lookup failure since that should return
> ECONNREFUSED.  Could it be that this hang is a separate bug that's
> not related to rhashtable?
> 
> If that was the case then we simply need to get rid of dynamic
> rehashing.

Well, /proc/net/netlink consistently show same socket twice when I get a
hang :

At this moment I have more than one process blocked :

lpaa23:~# ps aux|grep addrinfo
root     10597  0.0  0.0   3696   376 pts/0    S    21:20   0:00 /bin/bash ./getaddrinfo_many.sh
root     10601  0.0  0.0   1172     4 pts/0    S    21:20   0:00 ./getaddrinfo 500
root     11449  0.0  0.0   3700   384 pts/0    S    21:17   0:00 /bin/bash ./getaddrinfo_many.sh
root     11454  0.0  0.0   1172     4 pts/0    S    21:17   0:00 ./getaddrinfo 500
root     21424  0.0  0.0   3696   376 pts/0    S+   21:30   0:00 /bin/bash ./getaddrinfo_many.sh
root     21425  0.0  0.0   3696   376 pts/0    S+   21:30   0:00 /bin/bash ./getaddrinfo_many.sh
root     21426  0.0  0.0   3744  2236 pts/0    S+   21:30   0:00 /bin/bash ./getaddrinfo_many.sh
root     21470  0.0  0.0   3704   384 pts/0    S+   21:30   0:00 /bin/bash ./getaddrinfo_many.sh
root     21476  0.0  0.0   1172     4 pts/0    S+   21:30   0:00 ./getaddrinfo 500
root     22241  0.0  0.0   2604  1280 pts/1    S+   21:36   0:00 grep addrinfo
root     37231  0.0  0.0   3696   376 pts/0    S    21:19   0:00 /bin/bash ./getaddrinfo_many.sh
root     37235  0.0  0.0   1172     4 pts/0    S    21:19   0:00 ./getaddrinfo 500
root     48499  0.0  0.0   3696  2804 pts/0    S+   21:28   0:00 /bin/bash ./getaddrinfo_many.sh

And only one of the socket is listed twice (ffff881f6eceb000)

Apparently this is the one _after_ kernel socket.

Does it ring a bell ?

lpaa23:~# cat /proc/net/netlink 
sk       Eth Pid    Groups   Rmem     Wmem     Dump     Locks     Drops     Inode
ffff881f6eceb000 0   11454  00000000 0        0        0 2        0        61386380
ffff881fe08aa400 0   10601  00000000 0        0        0 2        0        69235237
ffff881fd3c80c00 0   37235  00000000 0        0        0 2        0        65612209
ffff881fd5356400 0   21476  00000000 0        0        0 2        0        116743320
ffff881fe1d98400 0   0      00000000 0        0        0 2        0        3       
ffff881f6eceb000 0   11454  00000000 0        0        0 2        0        61386380     << double >>
ffff881fe1066400 8   0      00000000 0        0        0 2        0        13355   
ffff881fe1066400 8   0      00000000 0        0        0 2        0        13355   
ffff883fe1204800 9   0      00000000 0        0        0 2        0        2056    
ffff883fe1204800 9   0      00000000 0        0        0 2        0        2056    
ffff883feecf6400 10  0      00000000 0        0        0 2        0        9602    
ffff883fe1208000 11  0      00000000 0        0        0 2        0        2051    
ffff883fe1208000 11  0      00000000 0        0        0 2        0        2051    
ffff881fe0f4ac00 16  0      00000000 0        0        0 2        0        2054    
ffff881fe0f4ac00 16  0      00000000 0        0        0 2        0        2054    

  reply	other threads:[~2015-05-14  4:38 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  5:30 netlink & rhashtable status Eric Dumazet
2015-05-13  5:40 ` Herbert Xu
2015-05-13  6:15   ` Eric Dumazet
2015-05-13  6:20     ` Herbert Xu
2015-05-13 13:04       ` Eric Dumazet
2015-05-13 16:18         ` Eric Dumazet
2015-05-13 16:35           ` David Miller
2015-05-14  2:55             ` Herbert Xu
2015-05-14  2:53           ` Herbert Xu
2015-05-14  3:17             ` Eric Dumazet
2015-05-14  3:34               ` Herbert Xu
2015-05-14  3:58                 ` Eric Dumazet
2015-05-14  4:13                   ` Eric Dumazet
2015-05-14  4:16                     ` Herbert Xu
2015-05-14  4:21                       ` Herbert Xu
2015-05-14  4:38                         ` Eric Dumazet [this message]
2015-05-14  5:03                           ` Herbert Xu
2015-05-14  5:56                         ` Red Hat INTERNAL-ONLY kernel discussion list <rhkernel-list@redhat.com> Herbert Xu
2015-05-14  5:58                         ` netlink: Disable insertions/removals during rehash Herbert Xu
2015-05-14  6:02                           ` netlink: Kill bogus lock_sock in netlink_insert Herbert Xu
2015-05-15 16:49                             ` David Miller
2015-05-15 18:01                               ` Eric Dumazet
2015-05-16 16:50                                 ` Eric Dumazet
2015-05-16 20:58                                   ` David Miller
2015-05-15 17:02                             ` David Miller
2015-05-16 12:32                               ` Herbert Xu
2015-05-16 13:40                                 ` [net] netlink: Make autobind rover an atomic_t Herbert Xu
2015-05-16 13:50                                   ` [net] netlink: Reset portid after netlink_insert failure Herbert Xu
2015-05-16 21:09                                     ` David Miller
2015-05-16 21:08                                   ` [net] netlink: Make autobind rover an atomic_t David Miller
2015-05-17  2:45                                     ` [net-next] netlink: Use random autobind rover Herbert Xu
2015-05-18  3:44                                       ` David Miller
2015-05-14 14:37                           ` netlink: Disable insertions/removals during rehash Eric Dumazet
2015-05-15  0:06                             ` Herbert Xu
2015-05-20 23:53                               ` Thomas Graf
2015-05-21  0:31                                 ` Eric Dumazet
2015-05-15 17:02                           ` David Miller
2015-05-16 13:16                             ` Herbert Xu
2015-05-16 21:10                               ` David Miller
2015-06-04 16:27                                 ` Guenter Roeck
2015-06-04 18:59                                   ` David Miller
2015-06-04 20:44                                     ` Eric Dumazet
2015-06-04 20:58                                     ` Guenter Roeck
2015-06-05  3:52                                   ` Herbert Xu
2015-06-05  5:27                                     ` Guenter Roeck
2015-06-26 10:44                         ` netlink & rhashtable status Konstantin Khlebnikov
2015-06-27  7:09                           ` Herbert Xu
2015-05-14  4:17                     ` Eric Dumazet

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=1431578321.27831.43.camel@edumazet-glaptop2.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.