Bug#205234: marked as done (libc6: vsyslog() call hangs su and login)
Your message dated Wed, 5 Nov 2003 10:32:44 -0800
with message-id <[🔎] 20031105183244.GA23427@marge.v3.ca>
and subject line Bug#205099: Please check these bugs with the latest glibc
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 13 Aug 2003 15:04:14 +0000
>From nmatantsev@hotmail.com Wed Aug 13 10:02:27 2003
Return-path: <nmatantsev@hotmail.com>
Received: from sea2-f20.sea2.hotmail.com (hotmail.com) [207.68.165.20]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19mx8t-0004L5-00; Wed, 13 Aug 2003 10:02:27 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
Wed, 13 Aug 2003 08:02:26 -0700
Received: from 142.201.5.100 by sea2fd.sea2.hotmail.msn.com with HTTP;
Wed, 13 Aug 2003 15:02:26 GMT
X-Originating-IP: [142.201.5.100]
X-Originating-Email: [nmatantsev@hotmail.com]
From: "Nikita Matantsev" <nmatantsev@hotmail.com>
To: submit@bugs.debian.org
Bcc:
Subject: libc6: vsyslog() call hangs su and login
Date: Wed, 13 Aug 2003 11:02:26 -0400
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <Sea2-F208qrkgCeR9eJ00012fb4@hotmail.com>
X-OriginalArrivalTime: 13 Aug 2003 15:02:26.0802 (UTC) FILETIME=[E8B58D20:01C361AB]
Delivered-To: submit@bugs.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0
tests=BAYES_30,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_07_20
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_07_20 (1.174.2.15-2003-03-30-exp)
Package: libc6
Version: 2.3.2-2
After upgrading to this version of libc6 and rebooting, su or login do not
work anymore.
su hangs after prompting for password (or right away, if invoked as root),
regardless of whether the '-' option is given.
I am running Debian unstable; I tried this with at least 3 or 4 kernels. For
kernels 2.2.25, 2.4.20, 2.4.21 I was able to successfully login using GDM;
but su hung in all of them.
When I tried booting with the 2.6.0 testing kernel in unstable, I got a
chance to try text console login (X server wouldn't start due to its own
issues) - I could not login through console at all - login hung as well.
I also tried downgrading the login package, but that did not make any
difference.
I ran su using gdb and after it hung and I sent SIGINT to the process, the
backtrace was as follows:
#0 0x401e3b88 in __pthread_sigsuspend () from /lib/libpthread.so.0
#1 0x401e3999 in __pthread_wait_for_restart_signal () from
/lib/libpthread.so.0#2 0x401e5159 in __pthread_alt_lock () from
/lib/libpthread.so.0
#3 0x401e24e6 in pthread_mutex_lock () from /lib/libpthread.so.0
#4 0x4011dead in vsyslog () from /lib/libc.so.6
#5 0x40180289 in _log_err () from /lib/security/pam_unix.so
#6 0x4017ead7 in pam_sm_open_session () from /lib/security/pam_unix.so
#7 0x4004c9c8 in pam_fail_delay () from /lib/libpam.so.0
#8 0x4004cb18 in _pam_dispatch () from /lib/libpam.so.0
#9 0x4004e516 in pam_open_session () from /lib/libpam.so.0
#10 0x0804a780 in ?? ()
#11 0x080568c8 in ?? ()
Googling revealed that the pthread calls look like something to do with an
unitialized mutex, but that's just my guessing.
Downgrading libc6 to 2.3.1 fixed the problem.
This bug seems similar to bug #205099 - that one also involved a syslog call
and a hanging process.
Cheers!
Nick
_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
---------------------------------------
Received: (at 211621-done) by bugs.debian.org; 5 Nov 2003 18:33:22 +0000
>From jbailey@nisa.net Wed Nov 05 12:33:11 2003
Return-path: <jbailey@nisa.net>
Received: from marge.v3.ca [216.66.20.89]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AHSSs-0008G4-00; Wed, 05 Nov 2003 12:33:10 -0600
Received: from marge.v3.ca (localhost [127.0.0.1])
by marge.v3.ca (8.12.10/8.12.10/Debian-0) with ESMTP id hA5IWjda021849;
Wed, 5 Nov 2003 10:32:45 -0800
Received: (from jbailey@localhost)
by marge.v3.ca (8.12.10/8.12.10/Debian-0) id hA5IWiWs021842;
Wed, 5 Nov 2003 10:32:44 -0800
X-Authentication-Warning: marge.v3.ca: jbailey set sender to jbailey@nisa.net using -f
Date: Wed, 5 Nov 2003 10:32:44 -0800
From: Jeff Bailey <jbailey@nisa.net>
To: Juergen Kreileder <jk@blackdown.de>, 205099@bugs.debian.org
Cc: GOTO Masanori <gotom@debian.or.jp>,
Anthony DeRobertis <asd@suespammers.org>,
211621-submitter@bugs.debian.org, 211621-done@bugs.debian.org
Subject: Re: Bug#205099: Please check these bugs with the latest glibc
Message-ID: <[🔎] 20031105183244.GA23427@marge.v3.ca>
References: <[🔎] 80y8ux8ou1.wl@oris.opensource.jp> <333BCEB0-0E34-11D8-82E0-00039317863E@suespammers.org> <[🔎] 80k76e99o5.wl@oris.opensource.jp> <[🔎] 877k2eaedg.fsf@zaphod.blackdown.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[🔎] 877k2eaedg.fsf@zaphod.blackdown.de>
User-Agent: Mutt/1.5.4i
X-EMSscan-MailScanner: Found to be clean
X-EMSscan-MailScanner-SpamCheck: not spam, SpamAssassin (score=-9.009,
required 5, BAYES_00 -4.90, USER_AGENT_MUTT -4.11)
Delivered-To: 211621-done@bugs.debian.org
X-Spam-Status: No, hits=-7.3 required=4.0
tests=BAYES_30,EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
version=2.53-bugs.debian.org_2003_11_03
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_11_03 (1.174.2.15-2003-03-30-exp)
On Wed, Nov 05, 2003 at 06:56:11PM +0100, Juergen Kreileder wrote:
> > Hmm... so could you confirm that this bug is already fixed? These 3
> > bugs are marked as "grave", so we have to resolve ASAP. And the
> > trouble is debian-glibc maintainers can't reproduce the reoccurrence
> > of these bugs. I would like to close these bugs. If you and
> > "someone" think there still exist bugs, could you tell us? If not,
> > could I close these bugs?
> I was able to reproduce the lwres related RPC problem until a few days
> ago. It seems to be gone now, probably got fixed by the recent glibc
> updates.
Lovely, closing 211621 then. Thanks!
Tks,
Jeff Bailey
Reply to: