Your message dated Thu, 07 Mar 2019 21:36:24 +0000
with message-id <[email protected]>
and subject line Bug#922554: fixed in curl 7.64.0-2
has caused the Debian Bug report #922554,
regarding network-manager: NetworkManager continuously spinning, probably while 
checking for connectivity
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
922554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922554
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.14.4-4
Severity: normal

Dear Maintainer,

I've noticed network manager is consuming most of the cpu time on my
system. It seems to be caused by the connectivity checking code. The
symptoms are:

1. ltrace shows this repeating on and on:

exe->epoll_wait(15, 0xbfb0bba0, 1, 0)                                           
                                                                                
        = 0
exe->clock_gettime(0, 0xbfb0bb54, 1, 15)                                        
                                                                                
        = 0
exe->clock_gettime(1, 0xbfb0bb54, 1, 15)                                        
                                                                                
        = 0
exe->clock_gettime(7, 0xbfb0bb54, 1, 15)                                        
                                                                                
        = 0
exe->g_object_ref(0x15c1b58, 0x15adf20, 0x15a84b0, 0xb7a5acc6)                  
                                                                                
        = 0x15c1b58
exe->g_io_channel_unix_get_fd(0x1629fb0, 0x15adf20, 0x15a84b0, 0xb7a5acc6)      
                                                                                
        = 20
exe->curl_multi_socket_action(0x15c4900, 20, 2, 0xbfb0bd88)                     
                                                                                
        = 0
exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2, 0xbfb0bd88)                 
                                                                                
        = 0
exe->g_object_ref(0x15c1b58, 0x1612440, 0x1640dc0, 0xb7a5acc6)                  
                                                                                
        = 0x15c1b58
exe->g_io_channel_unix_get_fd(0x15e32b0, 0x1612440, 0x1640dc0, 0xb7a5acc6)      
                                                                                
        = 22
exe->curl_multi_socket_action(0x15c4900, 22, 2, 0xbfb0bd88)                     
                                                                                
        = 0
exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2, 0xbfb0bd88)                 
                                                                                
        = 0
exe->g_object_ref(0x15c1b58, 0, 0x1654880, 0xb7a5acc6)                          
                                                                                
        = 0x15c1b58
exe->g_io_channel_unix_get_fd(0x1627080, 0, 0x1654880, 0xb7a5acc6)              
                                                                                
        = 24
exe->curl_multi_socket_action(0x15c4900, 24, 2, 0xbfb0bd88)                     
                                                                                
        = 0
exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2, 0xbfb0bd88)                 
                                                                                
        = 0

2. strace only shows incrementing and decrementing an eventfd, no
network activity or something.

poll([{fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=8, 
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN}, {fd=13, events=POLLIN}, {fd=14, 
events=POLLIN}, {fd=15, events=POLLIN}, {fd=16, events=POLLIN}, {fd=17, 
events=POLLIN}, {fd=20, events=POLLOUT}, {fd=22, events=POLLOUT}, {fd=24, 
events=POLLOUT}], 12, 0) = 4 ([{fd=3, revents=POLLIN}, {fd=20, 
revents=POLLOUT}, {fd=22, revents=POLLOUT}, {fd=24, revents=POLLOUT}])
read(3, "\6\0\0\0\0\0\0\0", 16)         = 8
epoll_wait(15, [], 1, 0)                = 0
clock_gettime(CLOCK_BOOTTIME, {tv_sec=124345, tv_nsec=994550347}) = 0
write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
write(3, "\1\0\0\0\0\0\0\0", 8)         = 8

Note: fd 22 is

NetworkMa 20906 root   20u     IPv4    2035553      0t0     TCP   
debian:45852->senfter.debian.org:http (ESTABLISHED)

However the event loop doesn't seem to touch the connection in any
way. fds 20 and 24 are similar connections.

Do you have any ideas about this? I'm not very knowledgeable about curl,
but surely it shouldn't hog the glib main loop like that?

Regards
     Jiri Palecek

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-3-686-pae (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=cs_CZ, LC_CTYPE=cs_CZ (charmap=ISO-8859-2), LANGUAGE=cs_CZ 
(charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages network-manager depends on:
ii  adduser                3.116
ii  dbus                   1.12.12-1
ii  init-system-helpers    1.56
ii  libaudit1              1:2.8.4-2
ii  libbluetooth3          5.49-4
ii  libc6                  2.28-6
ii  libcurl3-gnutls        7.64.0-1
ii  libglib2.0-0           2.58.3-1
ii  libgnutls30            3.6.6-2
ii  libjansson4            2.12-1
ii  libmm-glib0            1.6.2-1
ii  libndp0                1.6-1+b1
ii  libnewt0.52            0.52.20-4
ii  libnm0                 1.14.4-4
ii  libpam-systemd         240-5
ii  libpolkit-agent-1-0    0.105-25
ii  libpolkit-gobject-1-0  0.105-25
ii  libpsl5                0.20.2-1
ii  libreadline7           7.0-5
ii  libselinux1            2.8-1+b1
ii  libsystemd0            240-5
ii  libteamdctl0           1.28-1
ii  libudev1               240-5
ii  libuuid1               2.33.1-0.1
ii  lsb-base               10.2018112800
ii  policykit-1            0.105-25
ii  udev                   240-5
ii  wpasupplicant          2:2.6-18

Versions of packages network-manager recommends:
pn  crda             <none>
pn  dnsmasq-base     <none>
ii  iptables         1.8.2-2+b1
ii  isc-dhcp-client  4.4.1-2
pn  modemmanager     <none>
pn  ppp              <none>

Versions of packages network-manager suggests:
pn  libteam-utils  <none>

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
no-auto-default=e0:cb:4e:c2:58:50,
[ifupdown]
managed=false


-- no debconf information

--- End Message ---
--- Begin Message ---
Source: curl
Source-Version: 7.64.0-2

We believe that the bug you reported is fixed in the latest version of
curl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alessandro Ghedini <[email protected]> (supplier of updated curl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 07 Mar 2019 20:02:35 +0000
Source: curl
Architecture: source
Version: 7.64.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini <[email protected]>
Changed-By: Alessandro Ghedini <[email protected]>
Closes: 922554
Changes:
 curl (7.64.0-2) unstable; urgency=medium
 .
   * Fix infinite loop when fetching URLs with unreachable IPv6 (Closes: 
#922554)
Checksums-Sha1:
 078d7e936f00ecebbe33ad1e1a8c7e373b6260e5 2687 curl_7.64.0-2.dsc
 6fd45a9a9123ea4deb439ab8b60716a5c4034209 29696 curl_7.64.0-2.debian.tar.xz
 9ae9a76eef3c67cb5d04f2a5f200e6e87dba3c6f 10823 curl_7.64.0-2_amd64.buildinfo
Checksums-Sha256:
 6997fa959166f0fdf5545313d307b453970c271df3d135accbbe08773fa3cbc2 2687 
curl_7.64.0-2.dsc
 6173fb436e8bcea616e9bfc29eaddb25498b3a95cd5451d4cef83d957217fabe 29696 
curl_7.64.0-2.debian.tar.xz
 091ae3251d6a1b36d33572188e5644e87ca050ac10f689f1cb642dd2e308498c 10823 
curl_7.64.0-2_amd64.buildinfo
Files:
 a2a2fe5098218bd44ed904367b0adc7d 2687 web optional curl_7.64.0-2.dsc
 8d53e33032244bc8a5cf6dbde713abbf 29696 web optional curl_7.64.0-2.debian.tar.xz
 a7a00fb0d32c8e3f0151afa051fc5c68 10823 web optional 
curl_7.64.0-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEEBsId305pBx+F583DbwzL4CFiRygFAlyBiaIRHGdoZWRvQGRl
Ymlhbi5vcmcACgkQbwzL4CFiRygqZBAApYzddv2AOJYGT3wdgDD8gW17FwZZ//qg
nNqLuw+6PoVXAvekqCowBPXvh8HReTJ4D2vZLfovyIzZ5aUTRMMeoccLG0jUp7nT
WNfSVjo2vMUDGxHxaQyvzSc9qCNnqarKXMIVAFnHOI7+xaHIs30OSiKOQh0qGhuh
SUZBcj5EL4elRpckbEWR6S8R/Y4gQiPGtbLpceY3eMC/leVvMucToLPnGJec3pBy
fnhydtpEiQThdBOSMMdcgYYa+x3PTaymo1dh12u0iG47ZBAdfdYEIXY5RQ0Tykop
+LFwopc7x24K1Bh8XfwIV7Mmxte/xM6sdpwy/L4aBWaZKZfC61NqZjnAKPKp1TDN
MIFF+WyzXoXMir94DhG7YzHB6sbX6YTOBb//rRIA9vjrABJPQdwlQTsWSMpxtYPB
kuJbkyloY9WG9q4CeloWsBXMsYnQa840KqITOpocL3stXJnUcQKfVrzQIgcQKdEG
Alp5/D7QKiPeF8HZK5NGylfQDMDiMm8BxpbgLtL/zIT0Ql338U/GiE/GThXfqMPA
/Qxjv+qWCZ/G4+BBiRBRNcPYPpJrVXczMer8xMGKslhP/siyC5uT+mgxYs7AUY3n
fz7eD07Ed5go5hjDrBiB3dV4SWqAEKm3iC5s0O1dNchC10msRPReEasdv1rwQp/V
12KdPSQBxmo=
=rbhE
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to