public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "myungjoo.ham at samsung dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/13862] Reuse of cached stack can cause bounds overrun of thread DTV
Date: Tue, 26 Nov 2013 08:14:00 -0000 [thread overview]
Message-ID: <bug-13862-131-GXaajdFWBm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13862-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13862
MyungJoo Ham <myungjoo.ham at samsung dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |myungjoo.ham at samsung dot com
--- Comment #7 from MyungJoo Ham <myungjoo.ham at samsung dot com> ---
(In reply to Ondrej Bilka from comment #6)
> Was this patch posted?
As it seems that the patch was not even made to the mailing list, I've posted.
We have been experiencing crashes related with this issue recently as well.
http://sourceware.org/ml/libc-alpha/2013-11/msg00759.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-26 8:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 22:47 [Bug dynamic-link/13862] New: " paul at vineyardnetworks dot com
2012-03-16 23:02 ` [Bug dynamic-link/13862] " paul at vineyardnetworks dot com
2012-03-18 0:02 ` ppluzhnikov at google dot com
2012-05-01 0:02 ` foelsche at sbcglobal dot net
2012-06-14 23:59 ` paul at vineyardnetworks dot com
2012-10-19 11:48 ` siddhesh at redhat dot com
2013-10-03 7:26 ` neleai at seznam dot cz
2013-11-26 8:14 ` myungjoo.ham at samsung dot com [this message]
2014-06-06 22:09 ` david.abdurachmanov at gmail dot com
2014-06-06 22:12 ` david.abdurachmanov at gmail dot com
2014-06-07 8:12 ` david.abdurachmanov at gmail dot com
2014-06-18 7:35 ` giulio.eulisse at gmail dot com
2014-06-26 13:49 ` fweimer at redhat dot com
2014-10-10 16:27 ` trt at alumni dot duke.edu
2014-10-10 16:47 ` david.abdurachmanov at gmail dot com
2014-10-10 17:29 ` paul at vineyardnetworks dot com
2014-11-26 17:39 ` hjl.tools at gmail dot com
2014-11-27 14:06 ` cvs-commit at gcc dot gnu.org
2014-11-27 15:22 ` david.abdurachmanov at gmail dot com
2014-11-27 15:27 ` hjl.tools at gmail dot com
2014-11-27 15:34 ` cvs-commit at gcc dot gnu.org
2014-11-27 16:40 ` david.abdurachmanov at gmail dot com
2014-11-27 21:45 ` cvs-commit at gcc dot gnu.org
2014-11-27 22:43 ` hjl.tools at gmail dot com
2014-11-27 23:56 ` cvs-commit at gcc dot gnu.org
2014-11-28 15:58 ` cvs-commit at gcc dot gnu.org
2014-11-28 16:00 ` cvs-commit at gcc dot gnu.org
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-13862-131-GXaajdFWBm@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).