public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17746] tilegx32: strstr can miss the end of the string
Date: Thu, 29 Jan 2015 13:22:00 -0000 [thread overview]
Message-ID: <bug-17746-131-upR7SAg7QJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17746-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17746
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
Flags| |security?
--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
Can you clarify the impact of the bug? Just one results from strstr, or a
crash due to reading past the end of the string, or …?
--
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-27213-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Jan 29 13:24:28 2015
Return-Path: <glibc-bugs-return-27213-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 14991 invoked by alias); 29 Jan 2015 13:24:27 -0000
Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <glibc-bugs.sourceware.org>
List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org>
List-Post: <mailto:glibc-bugs@sourceware.org>
List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: glibc-bugs-owner@sourceware.org
Delivered-To: mailing list glibc-bugs@sourceware.org
Received: (qmail 14898 invoked by uid 48); 29 Jan 2015 13:24:21 -0000
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/17814] Use-After-Free
Date: Thu, 29 Jan 2015 13:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields:
Message-ID: <bug-17814-131-E3r7gysVUU@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-17814-131@http.sourceware.org/bugzilla/>
References: <bug-17814-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-01/txt/msg00238.txt.bz2
Content-length: 262
https://sourceware.org/bugzilla/show_bug.cgi?id\x17814
--- Comment #3 from Andreas Schwab <schwab@linux-m68k.org> ---
"out of memory" is a special, statically allocated error string.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-01-29 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 19:49 [Bug libc/17746] New: " cmetcalf at ezchip dot com
2014-12-22 19:53 ` [Bug libc/17746] " cvs-commit at gcc dot gnu.org
2014-12-22 19:54 ` cmetcalf at ezchip dot com
2015-01-29 13:22 ` fweimer at redhat dot com [this message]
2015-01-29 14:37 ` cmetcalf at ezchip dot com
2015-01-29 14:44 ` fweimer at redhat 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-17746-131-upR7SAg7QJ@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).