public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anand.bhat at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18662] __GI__IO_str_underflow in __tz_convert path
Date: Mon, 13 Jul 2015 08:04:00 -0000 [thread overview]
Message-ID: <bug-18662-131-ubCdUMYgUu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18662-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18662
--- Comment #2 from Anand Bhat <anand.bhat at gmail dot com> ---
Calling threads continuously spins in the __GI_IO_str_underflow taking more
than 100% of CPU.
Main issue is there is an underflow in __tz_convert path which is dangerous
as it is widely used function.
Regards,
Anand
On Mon, Jul 13, 2015 at 1:30 PM, schwab@linux-m68k.org <
sourceware-bugzilla@sourceware.org> wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=18662
>
> Andreas Schwab <schwab@linux-m68k.org> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> Status|NEW |WAITING
>
> --- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
> What exactly is the issue?
>
> --
> You are receiving this mail because:
> You reported the bug.
>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-13 8:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 6:44 [Bug libc/18662] New: " anand.bhat at gmail dot com
2015-07-13 8:00 ` [Bug libc/18662] " schwab@linux-m68k.org
2015-07-13 8:04 ` anand.bhat at gmail dot com [this message]
2015-07-13 8:14 ` schwab@linux-m68k.org
2015-07-13 8:39 ` anand.bhat at gmail dot com
2015-07-24 11:34 ` fweimer at redhat dot com
2015-08-15 19:38 ` ppluzhnikov at google dot com
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=bug-18662-131-ubCdUMYgUu@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).