From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BUG: bsd pts now climbs continuously
Date: Tue, 10 Aug 2004 17:51:27 +0000 [thread overview]
Message-ID: <41190B1F.4020202@zytor.com> (raw)
In-Reply-To: <1092137890.16939.8.camel@localhost.localdomain>
Alan Cox wrote:
> On Maw, 2004-08-10 at 05:07, H. Peter Anvin wrote:
>
>>>ssh breaks at 9999 which is fun too. It runs out of buffer space
>>>although because its been properly coded it doesn't overrun it just
>>>starts corrupting utmp
>>>
>>
>>This I believe is a glibc bug, and really needs to be fixed.
>>Unfortunately glibc's handling of utmp is just incredibly broken.
>
>
> How remarkable given the snprintf line in question is in the sshd
> source code.
>
OK, that wasn't the bug I was thinking about, then :)
I was referring to the "line id" stuff in utmp, which really seems too
broken to live.
next prev parent reply other threads:[~2004-08-10 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 20:30 BUG: bsd pts now climbs continuously jdh
2004-08-09 21:17 ` Alan Cox
2004-08-10 4:07 ` H. Peter Anvin
2004-08-10 11:38 ` Alan Cox
2004-08-10 17:51 ` H. Peter Anvin [this message]
2004-08-09 22:48 ` Andrew Morton
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=41190B1F.4020202@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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 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.