public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/15618] Possible access beyond memory bounds in pthread_attr_getaffinity
Date: Thu, 13 Jun 2013 19:50:00 -0000	[thread overview]
Message-ID: <bug-15618-131-g3QHzkKdJ3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15618-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15618

Siddhesh Poyarekar <siddhesh at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Siddhesh Poyarekar <siddhesh at redhat dot com> ---
Fixed in master:

commit 5865a56bf4e31c5a152e46454367a99c5971ac02
Author: Siddhesh Poyarekar <siddhesh@redhat.com>
Date:   Fri Jun 14 01:20:06 2013 +0530

    Avoid access beyond memory bounds in pthread_attr_getaffinity_np

    Resolves BZ #15618.

    pthread_attr_getaffinity_np may write beyond bounds of the input
    cpuset buffer if the size of the input buffer is smaller than the
    buffer present in the input pthread attributes.  Fix is to copy to the
    extent of the minimum of the source and the destination.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-06-13 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-15618-131@http.sourceware.org/bugzilla/>
2013-06-13 18:54 ` siddhesh at redhat dot com
2013-06-13 19:50 ` siddhesh at redhat dot com [this message]
2014-06-13 15:06 ` 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-15618-131-g3QHzkKdJ3@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).