[Bug libc/12547] New: realloc(p, 0) violates C99

[Bug libc/12547] New: realloc(p, 0) violates C99

[msebor at gmail dot com]

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

           Summary: realloc(p, 0) violates C99
           Product: glibc
           Version: 2.13
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper.fsp@gmail.com
        ReportedBy: msebor@gmail.com


The C99 standard specifies that an implementation may return NULL from a call
to realloc(p, 0). However, in such a case a conforming implementation must
avoid freeing the space pointed to by p and a program must call free(p). The
test case below shows that glibc violates this C99 requirement, causing a
program to free the space twice. Note that this C99 requirement to avoid
freeing the pointer is in contrast to POSIX -- see the discussion on the
austin-group-l list starting with this post:
https://www.opengroup.org/sophocles/show_mail.tpl?CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=15252

$ cat <<EOF | gcc -xc - && ./a.out 
#include <stdlib.h>

int main(void) {
    void *p, *q;

    p = malloc(1);
    q = realloc(p, 0);

    if (p && !q)
        free(p);

    return 0;
}
EOF
*** glibc detected *** double free or corruption (fasttop): 0x0000000000501010
***
Aborted

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[drepper.fsp at gmail dot com]

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

Ulrich Drepper <drepper.fsp at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #1 from Ulrich Drepper <drepper.fsp at gmail dot com> 2011-03-11 01:11:45 UTC ---
There is no way this will be changed.  This is how it has been implemented
forever.  C should document existing practice.  Changing it would mean
introducing memory leaks.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[jsm28 at gcc dot gnu.org]

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

--- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> 2011-03-17 19:02:55 UTC ---
In view of the conclusion at the WG14 meeting today that C1X should stay with
the C99 semantics for realloc rather than reverting to the C90/POSIX semantics,
and the consequentially proposed changes for POSIX
http://austingroupbugs.net/view.php?id=374
this looks rather like a case for having different versions of realloc
depending on feature test macros (with strict conformance to newer POSIX
versions, or to C99 or C1X without features beyond ISO C, getting the C99
version, and other modes (and existing binaries) getting the C90 version).

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[eblake at redhat dot com]

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

Eric Blake <eblake at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eblake at redhat dot com

--- Comment #3 from Eric Blake <eblake at redhat dot com> 2011-03-24 17:09:54 UTC ---
http://austingroupbugs.net/view.php?id=400 has been created to track the
resolution of fixing POSIX to no longer conflict with C99; glibc input is
necessary to help determine the correct way to resolve the POSIX dilemma.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[eblake at redhat dot com]

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

--- Comment #4 from Eric Blake <eblake at redhat dot com> 2011-03-24 17:19:57 UTC ---
(In reply to comment #2)
> In view of the conclusion at the WG14 meeting today that C1X should stay with
> the C99 semantics for realloc rather than reverting to the C90/POSIX semantics,
> and the consequentially proposed changes for POSIX
> http://austingroupbugs.net/view.php?id=374
> this looks rather like a case for having different versions of realloc
> depending on feature test macros (with strict conformance to newer POSIX
> versions, or to C99 or C1X without features beyond ISO C, getting the C99
> version, and other modes (and existing binaries) getting the C90 version).

Given that glibc has already done this for other interfaces (witness
__xpg_strerror_r), I think it would be appropriate for a glibc patch that
introduced __xpg_realloc for strict compliance.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[jakub at redhat dot com]

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

Jakub Jelinek <jakub at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at redhat dot com

--- Comment #5 from Jakub Jelinek <jakub at redhat dot com> 2011-03-24 17:23:15 UTC ---
For realloc that is more difficult, as realloc is often interposed.
Plus it is going to break lots of programs, which assume realloc (x, 0) is like
free (x).  I don't think we should change glibc.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[bruno at clisp dot org]

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

Bruno Haible <bruno at clisp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bruno at clisp dot org

--- Comment #6 from Bruno Haible <bruno at clisp dot org> 2011-03-25 00:08:12 UTC ---
The behaviour of realloc(p, 0) is the same on Solaris 10, AIX 7.1,
HP-UX 11.11, OSF/1 5.1, mingw as on glibc systems.

The other behaviour (realloc(p, 0) returning normally non-NULL) is
present on FreeBSD, OpenBSD, Cygwin, IRIX.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[eblake at redhat dot com]

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

Eric Blake <eblake at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |

--- Comment #7 from Eric Blake <eblake at redhat dot com> 2011-04-01 22:51:34 UTC ---
We can't just blindly ignore the WG14 C committee - either we have to fight
them harder to get the C1x standard (now in draft balloting) fixed, or we'll
have to give in and implement something like __xpg_realloc :(

Would anyone be willing to implement a systemtap probe to find out how many
programs in real life actually use realloc(p,0) in the first place, to see the
extent of the damage control if we are forced to change semantics?



Sent to the SC22WG14 email reflector:

The Austin Group has been studying this problem (see
http://austingroupbugs.net/view.php?id=400) [^] and trying to resolve any
conflict with C. This was also examined by WG14 during the London meeting,
where the resolution was "POSIX should conform to the requirements of C". The
Austin Group agrees with this resolution.

However, during our discussions, we have found the following in the C standard
(using refs to C99, not C1x):

Point 1: Objects cannot be zero sized.
6.2.6.1(2) Except for bit-fields, objects are composed of contiguous sequences
of one or more bytes,

Point 2: realloc(NULL, 0) is required to behave like malloc(0), and malloc
states "7.20.3.3(2) The malloc function allocates space for an object whose
size is specified by size and whose value is indeterminate." Since objects
cannot be zero sized, returning a non-null pointer is at best questionable.
However, this argues that realloc(p, 0) should always fail.

Point 3: Explicit permission to succeed AND return NULL is granted: "7.20.3(1)
If the size of the space requested is zero, the behavior is implementation-
defined: either a null pointer is returned, or the behavior is as if the size
were some nonzero value, except that the returned pointer shall not be used to
access an object." [this refers to calloc, malloc and realloc]. It has been
claimed that if realloc(p,0) returns a null pointer, that indicates that "the
new object cannot be allocated" and so the old object remains alive. However,
that interpretation is not clear, and the two separate sentences in 7.20.3.1
about null pointers are distinct cases, and the second does not necessarily
imply the first.

The POSIX words currently follow the original C89 text, and not the C99 update.
They state: "If size is 0 and ptr is not a null pointer,
the object pointed to is freed. ...RETURNS... If size is 0, either a null
pointer or a unique pointer that can be successfully passed to free() shall be
returned." The C99 words state "7.20.3.4(2) The realloc function deallocates
the old object pointed to by ptr and returns a pointer to a new object that has
the size specified by size." This would appear to allow an implementation to
deallocate the space and then return NULL (without setting errno).
Additionally, "7.20.3(3) ... or if the space has been deallocated by a call to
the free or realloc function..." strongly suggests that realloc(ptr, 0) is a
valid way to free ptr.

So, the Austin Group currently does not believe that POSIX conflicts with C,
and that it is permissible for realloc(p, 0) (where p is non-NULL) to free the
space allocated and return NULL. In POSIX, it is acceptable to set errno to
zero before the call, and test it afterwards to see if the pointer has been
freed or not.

Our current survey has shown that the following implementations free the
pointer and return NULL :

Glibc (GNU/Linux)
AIX
HP-UX
Solaris
OSF/1

There is strong resistance from at least one of these to changing their
implementation, in the belief that this would make current, memory leak free,
conforming code become both non-conforming and leaking.

-- 
Nick Stoughton
Austin Group/WG14 Liaison


    Reply on SC22WG14 reflector:

What WG 14 has been saying is that that interpretation is
incorrect. Referencing the latest C1x draft:

1. 7.22.3.5p4, "Returns," states "The realloc function returns a
pointer to the new object (which may have the same value as a pointer to
the old object), or a null pointer if the new object could not be
allocated." In other words, null means failure.

2. 7.22.3p1 states "If the space cannot be allocated, a null pointer is
returned. If the size of the space requested is zero, the behavior is
implementation-defined: either a null pointer is returned, or the
behavior is as if the size were some nonzero value, except that the
returned pointer shall not be used to access an object." This, together
with the previous quote, means that the function can either succeed and
return a valid pointer, or fail and return a null pointer.

3. 7.22.3.5p1 states "If memory for the new object cannot be allocated,
the old object is not deallocated and its value is unchanged." This,
together with the previous two quotes, means that if a null pointer is
returned, the operation has failed and the old object is not deallocated.

      You mentioned the fact that objects cannot be zero sized. That is
why the wording is the way it is. If we had zero-sized objects, we
could just say that an allocation of size zero returns a pointer to just
past the end of a zero-sized object (and that is why the pointer cannot
be dereferenced). Instead, we have to say the same thing without
talking about zero-sized objects.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[drepper.fsp at gmail dot com]

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

Ulrich Drepper <drepper.fsp at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #8 from Ulrich Drepper <drepper.fsp at gmail dot com> 2011-04-01 23:40:23 UTC ---
> We can't just blindly ignore the WG14 C committee

Yes, we can.

This is not the first time standards committees do something stupid and not the
first time they get ignored.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[nick at usenix dot org]

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

Nick Stoughton <nick at usenix dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nick at usenix dot org

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug libc/12547] realloc(p, 0) violates C99

[jackie.rosen at hushmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

Jackie Rosen <jackie.rosen at hushmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jackie.rosen at hushmail dot com

--- Comment #9 from Jackie Rosen <jackie.rosen at hushmail dot com> ---
*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugzilla.

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

[Bug libc/12547] realloc(p, 0) violates C99

[schwab at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

Andreas Schwab <schwab at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|jackie.rosen at hushmail dot com   |

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

[Bug libc/12547] realloc(p, 0) violates C99

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

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

[Bug libc/12547] realloc(p, 0) violates C99

[bugdal at aerifal dot cx]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

Rich Felker <bugdal at aerifal dot cx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |bugdal at aerifal dot cx
         Resolution|WONTFIX                     |---

--- Comment #10 from Rich Felker <bugdal at aerifal dot cx> ---
Reopening. Can this be reconsidered now that decision making is consensus based
and non-hostile to standards?

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

[Bug libc/12547] realloc(p, 0) violates C99

[joseph at codesourcery dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

--- Comment #11 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The proposed TC for DR#400 (closed, presumably to be published in C11 TC2) 
makes the standard say "If size is zero and memory for the new object is 
not allocated, it is implementation-defined whether the old object is 
deallocated. ... The realloc function returns a pointer to the new object 
(which may have the same value as a pointer to the old object), or a null 
pointer if the new object has not been allocated.  ... Invoking realloc 
with a size argument equal to zero is an obsolescent feature.".

Based on that conclusion about what realloc may do in this case, this 
sounds like INVALID to me.

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

[Bug libc/12547] realloc(p, 0) violates C99

[bugdal at aerifal dot cx]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

--- Comment #12 from Rich Felker <bugdal at aerifal dot cx> ---
I don't think it's so clear-cut. While the committee's decision to enshrine
this ugly historical behavior as allowable implementation-defined behavior
means glibc will be conforming to C11+TC2, conformance with older versions of
the standard (which glibc usually aims for) is left unresolved. But more
importantly, the committee's decision to make realloc(p,0)
implementation-defined and obsolescent means applications should stop using it,
because it's unsafe; therefore, I think glibc's priority should be minimizing
the danger.

Programs that expect glibc's historical behavior will experience only memory
leaks if compiled and run on systems that conform to C99 or present C11. On the
other hand, programs that expect the standard C99 behavior but run on current
glibc will exhibit double-free errors, a major source of security flaws. Being
that correct programs should not be using realloc(p,0) anyway, I think memory
leaks are a much lesser evil than double-free.

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

[Bug libc/12547] realloc(p, 0) violates C99

[bruno at clisp dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

--- Comment #13 from Bruno Haible <bruno at clisp dot org> ---
> I think memory leaks are a much lesser evil than double-free.

I disagree. Double-free errors get noticed and reported and therefore fixed
rather quickly. Memory leaks don't. => They are the longer-lasting evil.

But since the standard will say "Invoking realloc with a size argument equal to
zero is an obsolescent feature." glibc could give a warning about this case, if
some debugging flag is enabled (e.g. mtrace or valgrind?).

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

[Bug libc/12547] realloc(p, 0) violates C99

[bugdal at aerifal dot cx]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

--- Comment #14 from Rich Felker <bugdal at aerifal dot cx> ---
Double-free is not easily detected except in the case where both frees take
place in sequence with no intervening allocations. For example, in a case like
this:

void *p = malloc(n);
realloc(p, 0);
void *q = malloc(n);
free(p);

it's very likely that line 4 will end up freeing the allocation made in line 3.
The resulting state is extremely dangerous and almost always leads to arbitrary
code execution if enough effort is put into the analysis.

Memory leaks, on the other hand, are at worst a DoS issue.

Marking of a feature as "obsolescent" does not grant the implementation
permission to do crazy things like printing messages. It's purely a warning to
applications that the interface may be removed, or its behavior may become
undefined, in future versions of the language standard. Code using it is still
perfectly valid and conforming to the current language standard.

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

[Bug malloc/12547] realloc(p, 0) violates C99

[jsm28 at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|libc                        |malloc

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

[Bug malloc/12547] realloc(p, 0) violates C99

[bugdal at aerifal dot cx]

https://sourceware.org/bugzilla/show_bug.cgi?id=12547

--- Comment #17 from Rich Felker <bugdal at aerifal dot cx> ---
FYI the identical issue in Bionic has resulted in a RCE in WhatsApp:

https://awakened1712.github.io/hacking/hacking-whatsapp-gif-rce/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46354-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Oct 03 14:27:14 2019
Return-Path: <glibc-bugs-return-46354-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 34460 invoked by alias); 3 Oct 2019 14:27:14 -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 34418 invoked by uid 48); 3 Oct 2019 14:27:09 -0000
From: "bradley.gamble at ncipher dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25050] MB_LEN_MAX incorrect when compiling with _FORTIFY_SOURCE for PowerPC
Date: Thu, 03 Oct 2019 14:27: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: 2.29
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bradley.gamble at ncipher dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25050-131-Xh23XTywaF@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25050-131@http.sourceware.org/bugzilla/>
References: <bug-25050-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00012.txt.bz2
Content-length: 3860

https://sourceware.org/bugzilla/show_bug.cgi?id=25050

--- Comment #4 from Bradley Gamble <bradley.gamble at ncipher dot com> ---
My limits.h is sensible - It contains the correct definitions, for example
(truncated output):

#ifndef _LIBC_LIMITS_H_                                                         
#define _LIBC_LIMITS_H_ 1                                                       

#define __GLIBC_INTERNAL_STARTING_HEADER_IMPLEMENTATION                         
#include <bits/libc-header-start.h>                                             


/* Maximum length of any multibyte character in any locale.                     
   We define this value here since the gcc header does not define               
   the correct value.  */                                                       
#define MB_LEN_MAX      16                                                      


/* If we are not using GNU CC we have to define all the symbols ourself.        
   Otherwise use gcc's definitions (see below).  */                             
#if !defined __GNUC__ || __GNUC__ < 2                                           

/* We only protect from multiple inclusion here, because all the other          
   #include's protect themselves, and in GCC 2 we may #include_next through     
   multiple copies of this file before we get to GCC's.  */                     
# ifndef _LIMITS_H                                                              
#  define _LIMITS_H     1                                                       

#include <bits/wordsize.h>

My limitx.h only contains the following:

#ifndef _GCC_LIMITS_H_  /* Terminated in limity.h.  */                          
#define _GCC_LIMITS_H_                                                          

#ifndef _LIBC_LIMITS_H_                                                         
/* Use "..." so that we find syslimits.h only in this same directory.  */       
#include "syslimits.h"                                                          
#endif

Is there a step I am missing to perform this? I've tried multiple scripts for
cross-compilation and they all encounter this error with -DFORTIFY_SOURCE=2
enabled.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46357-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:01:17 2019
Return-Path: <glibc-bugs-return-46357-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 83839 invoked by alias); 4 Oct 2019 21:01:16 -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 82180 invoked by uid 55); 4 Oct 2019 21:01:11 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/16634] Application calling dlopen("./a.out",...) may run into  _dl_allocate_tls_init: Assertion `listp != ((void *)0)' failed!
Date: Fri, 04 Oct 2019 21:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-16634-131-XoUuKI706f@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16634-131@http.sourceware.org/bugzilla/>
References: <bug-16634-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00015.txt.bz2
Content-length: 1229

https://sourceware.org/bugzilla/show_bug.cgi?id=16634

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Florian Weimer <fw@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=77523d5e43cb5721c23855eb6045b0607a3b30a0

commit 77523d5e43cb5721c23855eb6045b0607a3b30a0
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri Oct 4 21:23:51 2019 +0200

    elf: Assign TLS modid later during dlopen [BZ #24930]

    Commit a42faf59d6d9f82e5293a9ebcc26d9c9e562b12b ("Fix BZ #16634.")
    attempted to fix a TLS modid consistency issue by adding additional
    checks to the open_verify function.  However, this is fragile
    because open_verify cannot reliably predict whether
    _dl_map_object_from_fd will later fail in the more complex cases
    (such as memory allocation failures).  Therefore, this commit
    assigns the TLS modid as late as possible.  At that point, the link
    map pointer will eventually be passed to _dl_close, which will undo
    the TLS modid assignment.

    Reviewed-by: Gabriel F. T. Gomes <gabrielftg@linux.ibm.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46355-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:01:11 2019
Return-Path: <glibc-bugs-return-46355-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 78938 invoked by alias); 4 Oct 2019 21:01:06 -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 74008 invoked by uid 55); 4 Oct 2019 21:01:01 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/24900] ld.so: Explicit loader invocation results in argv[0] in l_libname of main map
Date: Fri, 04 Oct 2019 21:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.31
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fweimer at redhat dot com
X-Bugzilla-Target-Milestone: 2.31
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields:
Message-ID: <bug-24900-131-kR2uZZdhWg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24900-131@http.sourceware.org/bugzilla/>
References: <bug-24900-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00013.txt.bz2
Content-length: 1140

https://sourceware.org/bugzilla/show_bug.cgi?id=24900

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Florian Weimer <fw@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2b26b084e4e4ba58a2ff9f8f8f14c9bca506bd59

commit 2b26b084e4e4ba58a2ff9f8f8f14c9bca506bd59
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri Oct 4 21:22:54 2019 +0200

    elf: Never use the file ID of the main executable [BZ #24900]

    If the loader is invoked explicitly and loads the main executable,
    it stores the file ID of the main executable in l_file_id.  This
    information is not available if the main excutable is loaded by the
    kernel, so this is another case where the two cases differ.

    This enhances commit 23d2e5faf0bca6d9b31bef4aa162b95ee64cbfc6
    ("elf: Self-dlopen failure with explict loader invocation
    [BZ #24900]").

    Reviewed-by: Carlos O'Donell <carlos@redhat.com>
    Reviewed-by: Gabriel F. T. Gomes <gabrielftg@linux.ibm.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46356-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:01:16 2019
Return-Path: <glibc-bugs-return-46356-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 83620 invoked by alias); 4 Oct 2019 21:01:16 -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 79974 invoked by uid 55); 4 Oct 2019 21:01:07 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/24930] dlopen of PIE executable can result in _dl_allocate_tls_init assertion failure
Date: Fri, 04 Oct 2019 21:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: fweimer at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-24930-131-g2Oy5ncfbz@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24930-131@http.sourceware.org/bugzilla/>
References: <bug-24930-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00014.txt.bz2
Content-length: 1229

https://sourceware.org/bugzilla/show_bug.cgi?id=24930

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Florian Weimer <fw@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=77523d5e43cb5721c23855eb6045b0607a3b30a0

commit 77523d5e43cb5721c23855eb6045b0607a3b30a0
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri Oct 4 21:23:51 2019 +0200

    elf: Assign TLS modid later during dlopen [BZ #24930]

    Commit a42faf59d6d9f82e5293a9ebcc26d9c9e562b12b ("Fix BZ #16634.")
    attempted to fix a TLS modid consistency issue by adding additional
    checks to the open_verify function.  However, this is fragile
    because open_verify cannot reliably predict whether
    _dl_map_object_from_fd will later fail in the more complex cases
    (such as memory allocation failures).  Therefore, this commit
    assigns the TLS modid as late as possible.  At that point, the link
    map pointer will eventually be passed to _dl_close, which will undo
    the TLS modid assignment.

    Reviewed-by: Gabriel F. T. Gomes <gabrielftg@linux.ibm.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46358-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:08:15 2019
Return-Path: <glibc-bugs-return-46358-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 13471 invoked by alias); 4 Oct 2019 21:08:15 -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 13406 invoked by uid 48); 4 Oct 2019 21:08:12 -0000
From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/24813] <asm/sigcontext.h> and <signal.h> are mutually incompatible on Linux
Date: Fri, 04 Oct 2019 21:08: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: 2.29
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: woodard at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: cc
Message-ID: <bug-24813-131-rxcrHMGC4t@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24813-131@http.sourceware.org/bugzilla/>
References: <bug-24813-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00016.txt.bz2
Content-length: 394

https://sourceware.org/bugzilla/show_bug.cgi?id=24813

Ben Woodard <woodard at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |woodard at redhat dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46359-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:41:38 2019
Return-Path: <glibc-bugs-return-46359-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 80728 invoked by alias); 4 Oct 2019 21:41:38 -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 80694 invoked by uid 48); 4 Oct 2019 21:41:34 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/24930] dlopen of PIE executable can result in _dl_allocate_tls_init assertion failure
Date: Fri, 04 Oct 2019 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: fweimer at redhat dot com
X-Bugzilla-Target-Milestone: 2.31
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone flagtypes.name
Message-ID: <bug-24930-131-yAmMb7T89n@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24930-131@http.sourceware.org/bugzilla/>
References: <bug-24930-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00017.txt.bz2
Content-length: 637

https://sourceware.org/bugzilla/show_bug.cgi?id=24930

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.31
              Flags|                            |security-

--- Comment #2 from Florian Weimer <fweimer at redhat dot com> ---
Fixed in glibc 2.31.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46360-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:43:41 2019
Return-Path: <glibc-bugs-return-46360-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 82243 invoked by alias); 4 Oct 2019 21:43:41 -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 82192 invoked by uid 48); 4 Oct 2019 21:43:37 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/24914] support/xsigstack.c assumes non-excutable stack causing failures on HPPA
Date: Fri, 04 Oct 2019 21:43: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: fweimer at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-24914-131-CSPUUtY34x@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24914-131@http.sourceware.org/bugzilla/>
References: <bug-24914-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00018.txt.bz2
Content-length: 456

https://sourceware.org/bugzilla/show_bug.cgi?id=24914

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46362-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:46:37 2019
Return-Path: <glibc-bugs-return-46362-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 84714 invoked by alias); 4 Oct 2019 21:46:37 -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 84651 invoked by uid 48); 4 Oct 2019 21:46:33 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/25049] dlopen() fails to open a shared object with DT_AUXILIARY field
Date: Fri, 04 Oct 2019 21:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.28
X-Bugzilla-Keywords:
X-Bugzilla-Severity: critical
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-25049-131-TcqsMVLbLb@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25049-131@http.sourceware.org/bugzilla/>
References: <bug-25049-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00020.txt.bz2
Content-length: 456

https://sourceware.org/bugzilla/show_bug.cgi?id=25049

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46361-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:46:20 2019
Return-Path: <glibc-bugs-return-46361-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 84268 invoked by alias); 4 Oct 2019 21:46:20 -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 84203 invoked by uid 48); 4 Oct 2019 21:46:16 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/25051] aarch64, powerpc64 uses surplus static tls for dynamically loaded dsos
Date: Fri, 04 Oct 2019 21:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.28
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-25051-131-Y2W0kdlV6z@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25051-131@http.sourceware.org/bugzilla/>
References: <bug-25051-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00019.txt.bz2
Content-length: 456

https://sourceware.org/bugzilla/show_bug.cgi?id=25051

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46364-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:47:31 2019
Return-Path: <glibc-bugs-return-46364-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 85939 invoked by alias); 4 Oct 2019 21:47:31 -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 85891 invoked by uid 48); 4 Oct 2019 21:47:27 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25035] sbrk() failure handled poorly in tunables_strdup
Date: Fri, 04 Oct 2019 21:47: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: fweimer at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-25035-131-lyT216QV8j@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25035-131@http.sourceware.org/bugzilla/>
References: <bug-25035-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00022.txt.bz2
Content-length: 456

https://sourceware.org/bugzilla/show_bug.cgi?id=25035

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46363-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:47:19 2019
Return-Path: <glibc-bugs-return-46363-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 85404 invoked by alias); 4 Oct 2019 21:47:19 -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 85351 invoked by uid 48); 4 Oct 2019 21:47:15 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/25036] Update collation order for Swedish
Date: Fri, 04 Oct 2019 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: localedata
X-Bugzilla-Version: 2.32
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-25036-131-h9e123MBx6@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25036-131@http.sourceware.org/bugzilla/>
References: <bug-25036-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00021.txt.bz2
Content-length: 456

https://sourceware.org/bugzilla/show_bug.cgi?id=25036

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46365-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:47:45 2019
Return-Path: <glibc-bugs-return-46365-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 86309 invoked by alias); 4 Oct 2019 21:47:45 -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 86244 invoked by uid 48); 4 Oct 2019 21:47:41 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/25030] RFE: malloc() cache line alignment for larger allocations
Date: Fri, 04 Oct 2019 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: malloc
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: cc component flagtypes.name
Message-ID: <bug-25030-131-0PtyUlieVB@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25030-131@http.sourceware.org/bugzilla/>
References: <bug-25030-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00023.txt.bz2
Content-length: 512

https://sourceware.org/bugzilla/show_bug.cgi?id=25030

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
          Component|libc                        |malloc
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46366-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:48:29 2019
Return-Path: <glibc-bugs-return-46366-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 87635 invoked by alias); 4 Oct 2019 21:48:21 -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 87410 invoked by uid 48); 4 Oct 2019 21:48:06 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/25026] Internal use of __itimer_which_t causing warnings/errors in POSIX-compliant code
Date: Fri, 04 Oct 2019 21:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: time
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-25026-131-j4cK5YRuud@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25026-131@http.sourceware.org/bugzilla/>
References: <bug-25026-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00024.txt.bz2
Content-length: 456

https://sourceware.org/bugzilla/show_bug.cgi?id=25026

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46367-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:50:37 2019
Return-Path: <glibc-bugs-return-46367-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 89364 invoked by alias); 4 Oct 2019 21:50:37 -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 89287 invoked by uid 48); 4 Oct 2019 21:50:33 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25003] getconf: POSIX_V7_THREADS_CFLAGS and POSIX_V7_THREADS_LDFLAGS missing
Date: Fri, 04 Oct 2019 21:50: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: fweimer at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-25003-131-vZ72FgSYZ8@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25003-131@http.sourceware.org/bugzilla/>
References: <bug-25003-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00025.txt.bz2
Content-length: 456

https://sourceware.org/bugzilla/show_bug.cgi?id=25003

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46369-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:52:56 2019
Return-Path: <glibc-bugs-return-46369-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 92776 invoked by alias); 4 Oct 2019 21:52:56 -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 92595 invoked by uid 48); 4 Oct 2019 21:52:52 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/24994] $LIB (DL_DST_LIB) is incorrect on multiarch systems
Date: Fri, 04 Oct 2019 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.30
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-24994-131-M7wecx3mmX@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24994-131@http.sourceware.org/bugzilla/>
References: <bug-24994-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00027.txt.bz2
Content-length: 456

https://sourceware.org/bugzilla/show_bug.cgi?id=24994

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46368-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 04 21:52:28 2019
Return-Path: <glibc-bugs-return-46368-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 92163 invoked by alias); 4 Oct 2019 21:52:26 -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 92108 invoked by uid 48); 4 Oct 2019 21:52:21 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/24998] #includes included inside extern C {} regions
Date: Fri, 04 Oct 2019 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: stdio
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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: cc flagtypes.name
Message-ID: <bug-24998-131-4njcM1DObb@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24998-131@http.sourceware.org/bugzilla/>
References: <bug-24998-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00026.txt.bz2
Content-length: 699

https://sourceware.org/bugzilla/show_bug.cgi?id=24998

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
              Flags|                            |security-

--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
It's likely this isn't the only case.

I think this will be easy to fix once we have the GCC warning in trunk (because
the installed headers test will fail due to -Werror).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46370-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat Oct 05 22:21:57 2019
Return-Path: <glibc-bugs-return-46370-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 26664 invoked by alias); 5 Oct 2019 22:21:57 -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 26597 invoked by uid 48); 5 Oct 2019 22:21:52 -0000
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/23296] Data race in setting function descriptor during lazy binding
Date: Sat, 05 Oct 2019 22:21: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: danglin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: attachments.created
Message-ID: <bug-23296-131-ScXU7ZzKhQ@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23296-131@http.sourceware.org/bugzilla/>
References: <bug-23296-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00028.txt.bz2
Content-length: 1552

https://sourceware.org/bugzilla/show_bug.cgi?id=23296

--- Comment #12 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 12019
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12019&action=edit
Patch to fix function descriptor race

The attached change adds support to fix the race in updating and accessing
function descriptors on hppa.  The approach used here is to modify binutils and
gcc so that indirect calls load and leave the function pointer for the call in
register %r22.  We also mark reloc offsets with a 1 in the least significant
bit of the offset.  If the runtime resolver is entered with a reloc offset
without a 1 in the least significant bit, we can then use the function pointer
in %r22 to find and update the descriptor.

The main race is a descriptor being updated between the load of the function
address and the global pointer.  However, PA 2.0 machines support out-of-order
execution of loads and stores, and can appear to execute out-of-order when
viewed from another processor.  I have revamped the code so glibc stores the
global pointer before the function address, and binutils and gcc generated code
load the function address before the global pointer.  We need to avoid the
situation where we branch to functions with an incorrect global pointer.  I've
never seen this happen but technically the function pointer store and load need
to be ordered (see page G-2 of PA-RISC Architecture).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46371-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat Oct 05 22:22:32 2019
Return-Path: <glibc-bugs-return-46371-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 27219 invoked by alias); 5 Oct 2019 22:22:31 -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 27170 invoked by uid 48); 5 Oct 2019 22:22:27 -0000
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/23296] Data race in setting function descriptor during lazy binding
Date: Sat, 05 Oct 2019 22:22: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: danglin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: attachments.created
Message-ID: <bug-23296-131-zdIF8Y24c0@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23296-131@http.sourceware.org/bugzilla/>
References: <bug-23296-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00029.txt.bz2
Content-length: 329

https://sourceware.org/bugzilla/show_bug.cgi?id=23296

--- Comment #13 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 12020
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12020&action=edit
Binutils patch

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46372-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat Oct 05 22:23:06 2019
Return-Path: <glibc-bugs-return-46372-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 27715 invoked by alias); 5 Oct 2019 22:23:06 -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 27641 invoked by uid 48); 5 Oct 2019 22:23:02 -0000
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/23296] Data race in setting function descriptor during lazy binding
Date: Sat, 05 Oct 2019 22:23: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: danglin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: attachments.created
Message-ID: <bug-23296-131-o4cc80UoJD@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23296-131@http.sourceware.org/bugzilla/>
References: <bug-23296-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00030.txt.bz2
Content-length: 324

https://sourceware.org/bugzilla/show_bug.cgi?id=23296

--- Comment #14 from John David Anglin <danglin at gcc dot gnu.org> ---
Created attachment 12021
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12021&action=edit
GCC patch

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46373-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat Oct 05 22:39:51 2019
Return-Path: <glibc-bugs-return-46373-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 58434 invoked by alias); 5 Oct 2019 22:39:50 -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 58388 invoked by uid 48); 5 Oct 2019 22:39:46 -0000
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/25066] New: FAIL: nptl/tst-tls1 on hppa
Date: Sat, 05 Oct 2019 22:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: nptl
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-25066-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00031.txt.bz2
Content-length: 1347

https://sourceware.org/bugzilla/show_bug.cgi?id=25066

            Bug ID: 25066
           Summary: FAIL: nptl/tst-tls1 on hppa
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: danglin at gcc dot gnu.org
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Created attachment 12022
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12022&action=edit
Patch to check stack alignment in clone

The nptl/tst-tls1 test calls pthread_create with a misaligned stack:

  /* Also check the alignment of the tls variables if a misaligned stack is
     specified.  */
  pthread_t th;
  void *thr_stack = NULL;
  thr_stack = xposix_memalign (0x200, STACK_SIZE + 1);
  xpthread_attr_setstack (&a, thr_stack + 1, STACK_SIZE);
  th = xpthread_create (&a, tf, NULL);
  xpthread_join (th);
  free (thr_stack);

This fails on hppa because the stack needs to be at least word aligned in
syscalls.

One possible fix is to check the stack alignment in clone.  But this doesn't
fix test.  However, as far as I can tell, it seem legit to reject a misaligned
stack.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46374-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Oct 08 13:58:31 2019
Return-Path: <glibc-bugs-return-46374-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 18082 invoked by alias); 8 Oct 2019 13:58:14 -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 17775 invoked by uid 48); 8 Oct 2019 13:58:01 -0000
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/20839] Incomplete rollback of dynamic linker state on linking failure
Date: Tue, 08 Oct 2019 13:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: carlos at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: cc see_also
Message-ID: <bug-20839-131-8G6qLhmjLE@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-20839-131@http.sourceware.org/bugzilla/>
References: <bug-20839-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00032.txt.bz2
Content-length: 549

https://sourceware.org/bugzilla/show_bug.cgi?id=20839

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com
           See Also|                            |https://bugzilla.redhat.com
                   |                            |/show_bug.cgi?id=1624941

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46375-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Oct 08 14:03:33 2019
Return-Path: <glibc-bugs-return-46375-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 130354 invoked by alias); 8 Oct 2019 14:03:32 -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 130218 invoked by uid 48); 8 Oct 2019 14:03:10 -0000
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/23462] Static binary with dynamic string tokens crashes.
Date: Tue, 08 Oct 2019 14:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.29
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: carlos at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: carlos at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-23462-131-H29JVV3OoM@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23462-131@http.sourceware.org/bugzilla/>
References: <bug-23462-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00033.txt.bz2
Content-length: 405

https://sourceware.org/bugzilla/show_bug.cgi?id=23462

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at sourceware dot org   |carlos at redhat dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46377-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Oct 08 14:04:41 2019
Return-Path: <glibc-bugs-return-46377-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 1526 invoked by alias); 8 Oct 2019 14:04:41 -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 1325 invoked by uid 48); 8 Oct 2019 14:04:21 -0000
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/23462] Static binary with dynamic string tokens crashes.
Date: Tue, 08 Oct 2019 14:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.29
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: carlos at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: carlos at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-23462-131-V8rkAQ9H0P@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23462-131@http.sourceware.org/bugzilla/>
References: <bug-23462-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00035.txt.bz2
Content-length: 508

https://sourceware.org/bugzilla/show_bug.cgi?id=23462

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
OK, so for real I'm going to post this. I dropped the ball.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46376-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Oct 08 14:04:41 2019
Return-Path: <glibc-bugs-return-46376-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 1410 invoked by alias); 8 Oct 2019 14:04:28 -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 1323 invoked by uid 48); 8 Oct 2019 14:04:21 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/23462] Static binary with dynamic string tokens crashes.
Date: Tue, 08 Oct 2019 14:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.29
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: carlos at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-23462-131-wl2j0cjwIT@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-23462-131@http.sourceware.org/bugzilla/>
References: <bug-23462-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00034.txt.bz2
Content-length: 508

https://sourceware.org/bugzilla/show_bug.cgi?id=23462

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
OK, so for real I'm going to post this. I dropped the ball.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46378-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Oct 08 22:18:59 2019
Return-Path: <glibc-bugs-return-46378-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 57911 invoked by alias); 8 Oct 2019 22:18:59 -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 57869 invoked by uid 48); 8 Oct 2019 22:18:55 -0000
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/25085] New: zic.c:1369:23: error: writing 4 bytes into a region of size 1
Date: Tue, 08 Oct 2019 22:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: time
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25085-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00036.txt.bz2
Content-length: 2478

https://sourceware.org/bugzilla/show_bug.cgi?id=25085

            Bug ID: 25085
           Summary: zic.c:1369:23: error: writing 4 bytes into a region of
                    size 1
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: time
          Assignee: unassigned at sourceware dot org
          Reporter: danglin at gcc dot gnu.org
  Target Milestone: ---

With gcc-10 (trunk), I see the following build error on hppa-unknown-linux-gnu:

 /home/dave/gnu/glibc/objdir/config.h -Wno-maybe-uninitialized
-Wno-unused-varia
ble        -I../include -I/home/dave/gnu/glibc/objdir/timezone 
-I/home/dave/gnu
/glibc/objdir  -I../sysdeps/unix/sysv/linux/hppa  -I../sysdeps/hppa/nptl 
-I../s
ysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux  -I../sysdeps/nptl
-I../sysdeps/pthread  -I../sysdeps/gnu  -I../sysdeps/unix/inet 
-I../sysdeps/unix/sysv  -I../sysdeps/unix  -I../sysdeps/posix 
-I../sysdeps/hppa/hppa1.1  -I../sysdeps/wordsize-32 
-I../sysdeps/ieee754/flt-32  -I../sysdeps/ieee754/dbl-64  -I../sysdeps/hppa/fpu
 -I../sysdeps/hppa  -I../sysdeps/ieee754  -I../sysdeps/generic  -I.. -I../libio
-I. -nostdinc -isystem
/home/dave/opt/test/lib/gcc/hppa-linux-gnu/10.0.0/include -isystem
/home/dave/opt/test/lib/gcc/hppa-linux-gnu/10.0.0/include-fixed -isystem
/usr/include  -D_LIBC_REENTRANT -include
/home/dave/gnu/glibc/objdir/libc-modules.h -DMODULE_NAME=nonlib -include
../include/libc-symbols.h       -DTOP_NAMESPACE=glibc -o
/home/dave/gnu/glibc/objdir/timezone/zic.o -MD -MP -MF
/home/dave/gnu/glibc/objdir/timezone/zic.o.dt -MT
/home/dave/gnu/glibc/objdir/timezone/zic.o
zic.c: In function 'inzsub':
zic.c:1369:23: error: writing 4 bytes into a region of size 1
[-Werror=stringop-overflow=]
 1369 |  z.z_format_specifier = cp ? *cp : '\0';
      |  ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~
zic.c:124:8: note: destination object declared here
  124 |  char  z_format_specifier;
      |        ^~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[2]: *** [../o-iterator.mk:9: /home/dave/gnu/glibc/objdir/timezone/zic.o]
Error 1
make[2]: Leaving directory '/home/dave/gnu/glibc/glibc/timezone'
make[1]: *** [Makefile:429: timezone/others] Error 2
make[1]: Leaving directory '/home/dave/gnu/glibc/glibc'
make: *** [Makefile:9: all] Error 2

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46379-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Oct 08 22:22:51 2019
Return-Path: <glibc-bugs-return-46379-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 60658 invoked by alias); 8 Oct 2019 22:22:51 -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 60595 invoked by uid 55); 8 Oct 2019 22:22:48 -0000
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/25085] zic.c:1369:23: error: writing 4 bytes into a region of size 1
Date: Tue, 08 Oct 2019 22:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: time
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25085-131-HoFQQ8Oq5A@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25085-131@http.sourceware.org/bugzilla/>
References: <bug-25085-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00037.txt.bz2
Content-length: 315

https://sourceware.org/bugzilla/show_bug.cgi?id=25085

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Have you have sure you are using GCC trunk r276711 or later?  (See GCC bug 
92014.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46380-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Oct 08 22:51:10 2019
Return-Path: <glibc-bugs-return-46380-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 90671 invoked by alias); 8 Oct 2019 22:51:10 -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 90632 invoked by uid 48); 8 Oct 2019 22:51:06 -0000
From: "danglin at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug time/25085] zic.c:1369:23: error: writing 4 bytes into a region of size 1
Date: Tue, 08 Oct 2019 22:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: time
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25085-131-M2Wmm3U0DM@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25085-131@http.sourceware.org/bugzilla/>
References: <bug-25085-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00038.txt.bz2
Content-length: 313

https://sourceware.org/bugzilla/show_bug.cgi?id=25085

--- Comment #2 from John David Anglin <danglin at gcc dot gnu.org> ---
I suspect this is resolved by Martin's fix for 92014.  My last gcc build was
with trunk revision 276654.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46381-listarch-glibc-bugs=sources.redhat.com@sourceware.org Wed Oct 09 15:45:02 2019
Return-Path: <glibc-bugs-return-46381-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 22167 invoked by alias); 9 Oct 2019 15:45:02 -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 19640 invoked by uid 48); 9 Oct 2019 15:44:57 -0000
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/25087] New: ldconfig mishandles unusual .dynstr placement
Date: Wed, 09 Oct 2019 15:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: dynamic-link
X-Bugzilla-Version: 2.30
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-25087-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00039.txt.bz2
Content-length: 2825

https://sourceware.org/bugzilla/show_bug.cgi?id=25087

            Bug ID: 25087
           Summary: ldconfig mishandles unusual .dynstr placement
           Product: glibc
           Version: 2.30
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: schwab@linux-m68k.org
  Target Milestone: ---

This library is mishandled by ldconfig, because .dynstr is located in a
separate LOAD segment, with a load offset different from the first LOAD
segment:

Elf file type is DYN (Shared object file)
Entry point 0x2280
There are 10 program headers, starting at offset 241664

Program Headers:
  Type           Offset             VirtAddr           PhysAddr
                 FileSiz            MemSiz              Flags  Align
  LOAD           0x0000000000000000 0x0000000000000000 0x0000000000000000
                 0x0000000000001a68 0x0000000000001a68  R      0x1000
  GNU_STACK      0x0000000000000000 0x0000000000000000 0x0000000000000000
                 0x0000000000000000 0x0000000000000000  RW     0x10
  NOTE           0x0000000000000238 0x0000000000000238 0x0000000000000238
                 0x0000000000000024 0x0000000000000024  R      0x4
  LOAD           0x0000000000002000 0x0000000000002000 0x0000000000002000
                 0x0000000000001201 0x0000000000001201  R E    0x1000
  LOAD           0x0000000000004000 0x0000000000004000 0x0000000000004000
                 0x0000000000000eb8 0x0000000000000eb8  R      0x1000
  GNU_EH_FRAME   0x00000000000048d8 0x00000000000048d8 0x00000000000048d8
                 0x0000000000000134 0x0000000000000134  R      0x4
  LOAD           0x0000000000005c68 0x0000000000006c68 0x0000000000006c68
                 0x00000000000003e8 0x0000000000000408  RW     0x1000
  GNU_RELRO      0x0000000000005c68 0x0000000000006c68 0x0000000000006c68
                 0x0000000000000398 0x0000000000000398  R      0x1
  LOAD           0x000000000003b000 0x0000000000008000 0x0000000000008000
                 0x0000000000000e80 0x0000000000000e80  RW     0x1000
  DYNAMIC        0x000000000003b230 0x0000000000008230 0x0000000000008230
                 0x0000000000000220 0x0000000000000220  RW     0x8

 Section to Segment mapping:
  Segment Sections...
   00     .note.gnu.build-id .hash .gnu.hash .dynsym .gnu.version
.gnu.version_r .rela.dyn .rela.plt 
   01     
   02     .note.gnu.build-id 
   03     .init .plt .plt.got .text .fini 
   04     .rodata .eh_frame_hdr .eh_frame 
   05     .eh_frame_hdr 
   06     .init_array .fini_array .got .data .bss 
   07     .init_array .fini_array .got 
   08     .dynamic .dynstr 
   09     .dynamic

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46382-listarch-glibc-bugs=sources.redhat.com@sourceware.org Wed Oct 09 23:43:24 2019
Return-Path: <glibc-bugs-return-46382-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 1263 invoked by alias); 9 Oct 2019 23:43:24 -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 1225 invoked by uid 48); 9 Oct 2019 23:43:20 -0000
From: "tg at mirbsd dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25093] New: sparc64 sigsetjmp buffer size mismatch
Date: Wed, 09 Oct 2019 23:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: libc
X-Bugzilla-Version: 2.32
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tg at mirbsd dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-25093-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00040.txt.bz2
Content-length: 1321

https://sourceware.org/bugzilla/show_bug.cgi?id=25093

            Bug ID: 25093
           Summary: sparc64 sigsetjmp buffer size mismatch
           Product: glibc
           Version: 2.32
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: tg at mirbsd dot de
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Created attachment 12036
  --> https://sourceware.org/bugzilla/attachment.cgi?id=12036&action=edit
patch

While reviewing a bug in µClibc-ng, which uses the same sigsetjmp structure as
glibc but actually uses the __mask_was_saved member during siglongjmp, I found
that said member was at offset 496, not 512 as expected (and therefore, the
structure was too short).

Looking at what it does, it calls the getcontext syscall, and the kernel side
of the structure has one more member in the FPU registers (which doesn’t exist
on sparc32 apparently and maybe therefore was missed?).

Adding the missing FPU member (patch attached) makes the offsetof the
__mask_was_saved member jump to 512 (at least in µClibc-ng, didn’t check
glibc).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46383-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Oct 10 10:06:59 2019
Return-Path: <glibc-bugs-return-46383-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 34721 invoked by alias); 10 Oct 2019 10:06:58 -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 34685 invoked by uid 48); 10 Oct 2019 10:06:54 -0000
From: "konrad.schwarz at siemens dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25094] New: A successful dlclose() seems to clear the last dynamic link error
Date: Thu, 10 Oct 2019 10:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
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: konrad.schwarz at siemens dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-25094-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00041.txt.bz2
Content-length: 1439

https://sourceware.org/bugzilla/show_bug.cgi?id=25094

            Bug ID: 25094
           Summary: A successful dlclose() seems to clear the last dynamic
                    link error
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: konrad.schwarz at siemens dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

https://pubs.opengroup.org/onlinepubs/9699919799.2008edition/functions/dlerror.html
states that dlerror() shall return a string that
"describes the last error that occurred during dynamic linking processing."

This would make the following code valid, assuming symbol_table is the
result of a successful dlopen():

   if (!dlsym (symbol_table, "bogus_function_name")) {
       dlclose (symbol_table);
       return dlerror ();
   }

However, a null string is returned to the invoker.

The spec goes on to say that:

  If no dynamic linking errors have occurred since the last invocation of 
  dlerror(), dlerror() shall return NULL. Thus, invoking dlerror() a second 
  time, immediately following a prior invocation, shall result in NULL being 
  returned.

However, that case does not apply to the code above.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46384-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Oct 10 10:25:06 2019
Return-Path: <glibc-bugs-return-46384-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 114379 invoked by alias); 10 Oct 2019 10:25:06 -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 114323 invoked by uid 48); 10 Oct 2019 10:25:02 -0000
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25094] A successful dlclose() seems to clear the last dynamic link error
Date: Thu, 10 Oct 2019 10:25: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-Resolution: INVALID
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-25094-131-xalpwTdjcK@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25094-131@http.sourceware.org/bugzilla/>
References: <bug-25094-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00042.txt.bz2
Content-length: 608

https://sourceware.org/bugzilla/show_bug.cgi?id=25094

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
dlclose is another use of "dynamic linking processing", and therefore affects
the value returned by dlerror.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46385-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Oct 10 10:44:33 2019
Return-Path: <glibc-bugs-return-46385-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 35944 invoked by alias); 10 Oct 2019 10:44:28 -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 35278 invoked by uid 48); 10 Oct 2019 10:44:23 -0000
From: "konrad.schwarz at siemens dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25094] A successful dlclose() seems to clear the last dynamic link error
Date: Thu, 10 Oct 2019 10:44: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: konrad.schwarz at siemens dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25094-131-l7jD18DgGK@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25094-131@http.sourceware.org/bugzilla/>
References: <bug-25094-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00043.txt.bz2
Content-length: 728

https://sourceware.org/bugzilla/show_bug.cgi?id=25094

--- Comment #2 from Konrad Schwarz <konrad.schwarz at siemens dot com> ---
Wording in POSIX contradicts above comment.

If dlclose() (or any other dynamic linking function) were allowed
to reset the dynamic linking error indication, the wording would
be along the lines
"describes the last result that occurred during dynamic linking
processing, a null pointer if no error occurred".

The actual wording requires behavior similar to errno,
which is modified *only* when an error occurs --
and the application is required to reset errno to zero
to detect error in some cases.

Please reopen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46386-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Oct 10 20:38:13 2019
Return-Path: <glibc-bugs-return-46386-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 38189 invoked by alias); 10 Oct 2019 20:38:13 -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 38129 invoked by uid 55); 10 Oct 2019 20:38:07 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18231] ipc_perm struct's mode member has wrong type in sys/ipc.h
Date: Thu, 10 Oct 2019 20:38: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: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: adhemerval.zanella at linaro dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields:
Message-ID: <bug-18231-131-2KULmq2EbK@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18231-131@http.sourceware.org/bugzilla/>
References: <bug-18231-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00044.txt.bz2
Content-length: 5519

https://sourceware.org/bugzilla/show_bug.cgi?id=18231

--- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Adhemerval Zanella
<azanella@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2f959dfe849e0646e27403f2e4091536496ac0f0

commit 2f959dfe849e0646e27403f2e4091536496ac0f0
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date:   Thu Oct 10 18:13:11 2019 +0000

    sysvipc: Set ipc_perm mode as mode_t (BZ#18231)

    This patch sets the mode field in ipc_perm as mode_t for all architectures,
    as POSIX specification [1].  The changes required are as follow:

      1. It moves the ipc_perm definition out of ipc.h to its own header
         ipc_perm.h.  It also allows consolidate the IPC_* definition on
         only one header.

      2. The generic implementation follow the kernel ipc64_perm size so the
         syscall can be made directly without temporary buffer copy.  However,
         since glibc defines the MODE field as mode_t, it omits the __PAD1
field
         (since glibc does not export mode_t as 16-bit for any architecture).

         It is a two-fold improvement:

         2.1. New implementation which follow Linux UAPI will not need to
          provide an arch-specific ipc-perm.h header neither wrongly
              use the wrong 16-bit definition from previous default ipc.h
          (as csky did).

         2.1. It allows consolidate ipc_perm definition for architectures that
              already provide mode_t as 32-bit.

      3. All kernel ABIs for the supported architectures already provides the
         expected padding for mode type extension to 32-bit.  However, some
         architectures the padding has the wrong placement, so it requires
         the ipc control routines (msgctl, semctl, and shmctl) to adjust the
         mode field accordingly.  Currently they are armeb, microblaze, m68k,
         s390, and sheb.

         A new assume is added, __ASSUME_SYSVIPC_BROKEN_MODE_T, which the
         required ABIs define.

      4. For the ABIs that define __ASSUME_SYSVIPC_BROKEN_MODE_T, it also
         require compat symbols that do not adjust the mode field.

    Checked on arm-linux-gnueabihf, aarch64-linux-gnu, powerpc64le-linux-gnu,
    and x86_64-linux-gnu. I also checked the sysvipc tests on hppa-linux-gnu,
    sh4-linux-gnu, s390x-linux-gnu, and s390-linux-gnu.

    I also did a sanity test against armeb qemu usermode for the sysvipc
    tests.

        [BZ #18231]
        * sysdeps/unix/sysv/linux/Makefile (sysdep_headers): Add
        bits/ipc-perm.h.
        * sysdeps/unix/sysv/linux/aarch64/bits/ipc.h: Remove file.
        * sysdeps/unix/sysv/linux/alpha/bits/ipc.h: Likewise.
        * sysdeps/unix/sysv/linux/hppa/bits/ipc.h: Likewise.
        * sysdeps/unix/sysv/linux/ia64/bits/ipc.h: Likewise.
        * sysdeps/unix/sysv/linux/mips/bits/ipc.h: Likewise.
        * sysdeps/unix/sysv/linux/powerpc/bits/ipc.h: Likewise.
        * sysdeps/unix/sysv/linux/s390/bits/ipc.h: Likewise.
        * sysdeps/unix/sysv/linux/sparc/bits/ipc.h: Likewise.
        * sysdeps/unix/sysv/linux/arm/kernel-features.h
        [__BYTE_ORDER == __BIG_ENDIAN] (__ASSUME_SYSVIPC_BROKEN_MODE_T):
        Define.
        * sysdeps/sysv/linux/microblaze/kernel-features.h: Likewise.
        * sysdeps/unix/sysv/linux/s390/kernel-features.h
        [!__s390x__] (__ASSUME_SYSVIPC_BROKEN_MODE_T): Define.
        * sysdeps/unix/sysv/linux/sh/kernel-features.h
        (__ASSUME_SYSVIPC_BROKEN_MODE_T): Define.
        * sysdeps/unix/sysv/linux/m68k/kernel-features.h: Likewise.
        * sysdeps/unix/sysv/linux/bits/ipc-perm.h: New file.
        * sysdeps/unix/sysv/linux/powerpc/bits/ipc-perm.h: Likewise.
        * sysdeps/unix/sysv/linux/sparc/bits/ipc-perm.h: Likewise.
        * sysdeps/unix/sysv/linux/bits/ipc.h (ipc_perm): Move to
        bits/ipc-perm.h.
        * sysdeps/unix/sysv/linux/hppa/bits/ipc-perm.h: New file.
        * sysdeps/unix/sysv/linux/kernel-features.h: Add comment about
        __ASSUME_SYSVIPC_BROKEN_MODE_T semantic.
        * sysdeps/unix/sysv/linux/msgctl.c (DEFAULT_VERSION): Define as
        2.31 if __ASSUME_SYSVIPC_BROKEN_MODE_T is defined.
        (msgctl_syscall, __msgctl_mode16): New symbol.
        (__new_msgctl): Add bits for __ASSUME_SYSVIPC_BROKEN_MODE_T.
        * sysdeps/unix/sysv/linux/semctl.c: Likewise.
        * sysdeps/unix/sysv/linux/shmctl.c: Likewise.
        * sysdeps/unix/sysv/linux/arm/be/libc.abilist (GLIBC_2.31): Add
        msgctl, semctl, and shmctl.
        * sysdeps/sysv/linux/microblaze/be/libc.abilist: Likewise.
        * sysdeps/unix/sysv/linux/m68k/coldfire/libc.abilist: Likewise.
        * sysdeps/unix/sysv/linux/m68k/m680x0/libc.abilist: Likewise.
        * sysdeps/unix/sysv/linux/s390/s390-32/libc.abilist: Likewise.
        * sysdeps/unix/sysv/linux/sh/be/libc.abilist: Likewise.
        * conform/data/sys/ipc.h-data: Only xfail {struct ipc_perm} mode_t
        mode for Hurd.
        * sysdeps/unix/sysv/linux/m68k/Versions (libc) [GLIBC_2.31]: Add
        msgctl, semctl, and shmctl.
        * sysdeps/unix/sysv/linux/arm/be/Versions: New file.
        * sysdeps/unix/sysv/linux/microblaze/be/Versions: Likewise.
        * sysdeps/unix/sysv/linux/sh/be/Versions: Likewise.

    [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/sys_ipc.h.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46387-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Oct 10 20:38:42 2019
Return-Path: <glibc-bugs-return-46387-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 38912 invoked by alias); 10 Oct 2019 20:38:42 -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 38856 invoked by uid 48); 10 Oct 2019 20:38:38 -0000
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/18231] ipc_perm struct's mode member has wrong type in sys/ipc.h
Date: Thu, 10 Oct 2019 20:38: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: adhemerval.zanella at linaro dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: adhemerval.zanella at linaro dot org
X-Bugzilla-Target-Milestone: 2.31
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-18231-131-DiCHtYDEin@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-18231-131@http.sourceware.org/bugzilla/>
References: <bug-18231-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00045.txt.bz2
Content-length: 647

https://sourceware.org/bugzilla/show_bug.cgi?id=18231

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.31

--- Comment #7 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
Fixed on 2.31 (2f959dfe849e0646e27403f2e4091536496ac0f0).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46389-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Oct 10 23:01:50 2019
Return-Path: <glibc-bugs-return-46389-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 39810 invoked by alias); 10 Oct 2019 23:01:50 -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 39779 invoked by uid 48); 10 Oct 2019 23:01:46 -0000
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/25097] new -Warray-bounds with GCC 10
Date: Thu, 10 Oct 2019 23:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: build
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc component
Message-ID: <bug-25097-131-7zYgq9KVvi@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25097-131@http.sourceware.org/bugzilla/>
References: <bug-25097-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00047.txt.bz2
Content-length: 447

https://sourceware.org/bugzilla/show_bug.cgi?id=25097

Martin Sebor <msebor at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com
          Component|nptl                        |build

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46388-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu Oct 10 23:01:03 2019
Return-Path: <glibc-bugs-return-46388-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 39282 invoked by alias); 10 Oct 2019 23:01:03 -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 39165 invoked by uid 48); 10 Oct 2019 23:00:57 -0000
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/25097] New: new -Warray-bounds with GCC 10
Date: Thu, 10 Oct 2019 23:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: nptl
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-25097-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00046.txt.bz2
Content-length: 18958

https://sourceware.org/bugzilla/show_bug.cgi?id=25097

            Bug ID: 25097
           Summary: new -Warray-bounds with GCC 10
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: msebor at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

Testing a GCC 10 -Warray-bounds enhancement triggers a bunch of warnings in
Glibc for accesses to interior zero-length array members.  As best I can tell
the warnings are correct -- they all point out out-of-bounds accesses to these
arrays -- but the Glibc code that triggers them seems to be written that way by
design.  It uses one member array to access another that follows it in the
structure layout.  This works in simple cases but it's not guaranteed to work
in others as GCC doesn't always avoid assuming that zero-length arrays don't
alias subsequent members.

The -Warray-bounds instances are these:
  fileops.c:337
  fileops.c:338
  fileops.c:339
  fileops.c:340
  iofwide.c:177
  iofwide.c:178
  iofwide.c:179
  iofwide.c:193
  iofwide.c:244
  iofwide.c:245
  iofwide.c:246
  iofwide.c:86
  iofwide.c:87
  iofwide.c:88
  iofwide.c:89
  libc-tls.c:209
  rtld.c:1016

The detailed warnings are below.  Unless the code can be changed to avoid this
type of "misuse" I think the best approach is to suppress the warnings via
#pragma GCC diagnostic ignored before each access.  The GCC enhancement is
still under review so this is an early heads up that it may be coming.

libc-tls.c:209:30: warning: array subscript 0 is above array bounds of ‘struct
dtv_slotinfo[]’ [-Warray-bounds]
  209 |   static_slotinfo.si.slotinfo[1].map = main_map;
In file included from ../sysdeps/x86/ldsodefs.h:64,
                 from ../sysdeps/gnu/ldsodefs.h:46,
                 from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
                 from libc-tls.c:21:
../sysdeps/generic/ldsodefs.h:423:7: note: while referencing ‘slotinfo’
  423 |     } slotinfo[0];
iofwide.c:86:25: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
   86 |  cc->__cd_in.__cd.__data[0].__invocation_counter = 0;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:87:25: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
   87 |  cc->__cd_in.__cd.__data[0].__internal_use = 1;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:88:25: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
   88 |  cc->__cd_in.__cd.__data[0].__flags = __GCONV_IS_LAST;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:89:25: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
   89 |  cc->__cd_in.__cd.__data[0].__statep = &fp->_wide_data->_IO_state;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:177:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  177 |   codecvt->__cd_in.__cd.__data[0].__outbuf = (unsigned char *)
to_start;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:178:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  178 |   codecvt->__cd_in.__cd.__data[0].__outbufend = (unsigned char *)
to_end;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:179:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  179 |   codecvt->__cd_in.__cd.__data[0].__statep = statep;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:193:54: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  193 |   *to_stop = (wchar_t *) codecvt->__cd_in.__cd.__data[0].__outbuf;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:244:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  244 |   codecvt->__cd_in.__cd.__data[0].__outbuf = (unsigned char *) to_buf;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:245:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  245 |   codecvt->__cd_in.__cd.__data[0].__outbufend = (unsigned char *)
&to_buf[max];
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:246:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  246 |   codecvt->__cd_in.__cd.__data[0].__statep = statep;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:86:25: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
   86 |  cc->__cd_in.__cd.__data[0].__invocation_counter = 0;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:87:25: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
   87 |  cc->__cd_in.__cd.__data[0].__internal_use = 1;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:88:25: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
   88 |  cc->__cd_in.__cd.__data[0].__flags = __GCONV_IS_LAST;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:89:25: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
   89 |  cc->__cd_in.__cd.__data[0].__statep = &fp->_wide_data->_IO_state;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:177:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  177 |   codecvt->__cd_in.__cd.__data[0].__outbuf = (unsigned char *)
to_start;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:178:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  178 |   codecvt->__cd_in.__cd.__data[0].__outbufend = (unsigned char *)
to_end;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:179:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  179 |   codecvt->__cd_in.__cd.__data[0].__statep = statep;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:193:54: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  193 |   *to_stop = (wchar_t *) codecvt->__cd_in.__cd.__data[0].__outbuf;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:244:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  244 |   codecvt->__cd_in.__cd.__data[0].__outbuf = (unsigned char *) to_buf;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:245:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  245 |   codecvt->__cd_in.__cd.__data[0].__outbufend = (unsigned char *)
&to_buf[max];
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
iofwide.c:246:31: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  246 |   codecvt->__cd_in.__cd.__data[0].__statep = statep;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from ../libio/libioP.h:45,
                 from iofwide.c:27:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
fileops.c:337:27: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  337 |    cc->__cd_in.__cd.__data[0].__invocation_counter = 0;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from libioP.h:45,
                 from fileops.c:29:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
fileops.c:338:27: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  338 |    cc->__cd_in.__cd.__data[0].__internal_use = 1;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from libioP.h:45,
                 from fileops.c:29:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
fileops.c:339:27: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  339 |    cc->__cd_in.__cd.__data[0].__flags = __GCONV_IS_LAST;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from libioP.h:45,
                 from fileops.c:29:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
fileops.c:340:27: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from libioP.h:45,
                 from fileops.c:29:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
fileops.c:337:27: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  337 |    cc->__cd_in.__cd.__data[0].__invocation_counter = 0;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from libioP.h:45,
                 from fileops.c:29:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
fileops.c:338:27: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  338 |    cc->__cd_in.__cd.__data[0].__internal_use = 1;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from libioP.h:45,
                 from fileops.c:29:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
fileops.c:339:27: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
  339 |    cc->__cd_in.__cd.__data[0].__flags = __GCONV_IS_LAST;
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from libioP.h:45,
                 from fileops.c:29:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
fileops.c:340:27: warning: array subscript 0 is above array bounds of ‘struct
__gconv_step_data[]’ [-Warray-bounds]
In file included from ../include/gconv.h:1,
                 from ../libio/libio.h:49,
                 from ../include/stdio.h:8,
                 from libioP.h:45,
                 from fileops.c:29:
../iconv/gconv.h:144:42: note: while referencing ‘__data’
  144 |   __extension__ struct __gconv_step_data __data[0];
          -Wl,--verbose 2>&1 | \
rtld.c:1016:27: warning: array subscript 0 is above array bounds of ‘struct
auditstate[]’ [-Warray-bounds]
 1016 |    GL(dl_rtld_map).l_audit[cnt].cookie = (intptr_t) &GL(dl_rtld_map);
In file included from ../include/dlfcn.h:4,
                 from rtld.c:20:
../include/link.h:335:7: note: while referencing ‘l_audit’
  335 |     } l_audit[0];

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46390-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 11 11:19:46 2019
Return-Path: <glibc-bugs-return-46390-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 32200 invoked by alias); 11 Oct 2019 11:19:46 -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 32102 invoked by uid 48); 11 Oct 2019 11:19:41 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/25098] New: nptl: ctype classification functions are not AS-Safe
Date: Fri, 11 Oct 2019 11:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: nptl
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone flagtypes.name
Message-ID: <bug-25098-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00048.txt.bz2
Content-length: 744

https://sourceware.org/bugzilla/show_bug.cgi?id=25098

            Bug ID: 25098
           Summary: nptl: ctype classification functions are not AS-Safe
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---
             Flags: security-

A signal can arrive on a new thread before __ctype_init has completed on that
thread.

Pointed out by Mathieu Desnoyers as part of the rseq work.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46391-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 11 18:21:38 2019
Return-Path: <glibc-bugs-return-46391-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 8780 invoked by alias); 11 Oct 2019 18:21:37 -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 8674 invoked by uid 48); 11 Oct 2019 18:21:34 -0000
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/25098] nptl: ctype classification functions are not AS-Safe
Date: Fri, 11 Oct 2019 18:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: nptl
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fweimer at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: fweimer at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security-
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-25098-131-HciddpzjI4@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25098-131@http.sourceware.org/bugzilla/>
References: <bug-25098-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00049.txt.bz2
Content-length: 464

https://sourceware.org/bugzilla/show_bug.cgi?id=25098

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|unassigned at sourceware dot org   |fweimer at redhat dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46392-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat Oct 12 03:00:34 2019
Return-Path: <glibc-bugs-return-46392-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 26825 invoked by alias); 12 Oct 2019 03:00:32 -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 26496 invoked by uid 48); 12 Oct 2019 03:00:15 -0000
From: "dj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/24949] High CPU load by nscd service
Date: Sat, 12 Oct 2019 03:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: nscd
X-Bugzilla-Version: 2.17
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dj at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: dj at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-24949-131-Ut3PyIdl9J@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-24949-131@http.sourceware.org/bugzilla/>
References: <bug-24949-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-10/txt/msg00050.txt.bz2
Content-length: 425

https://sourceware.org/bugzilla/show_bug.cgi?id=24949

--- Comment #2 from dj at redhat dot com <dj at redhat dot com> ---
I've been trying unsuccessfully to reproduce this.  Could you attach the
relevent nsswitch.conf and nscd.conf files?  Also, if you could run nscd with
"-d" and capture the output thereof, and attach that too?

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-46393-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sun Oct 13 23:21:47 2019
Return-Path: <glibc-bugs-return-46393-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 120676 invoked by alias); 13 Oct 2019 23:21:44 -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 120668 invoked by uid 89); 13 Oct 2019 23:21:44 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=2.5 required=5.0 tests=AWL,BAYES_50,HTML_IMAGE_RATIO_02,HTML_MESSAGE,KAM_SHORT,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=UD:amazonaws.com, H*Ad:U*glibc-bugs, HTo:U*glibc-bugs, promo
X-HELO: ecmme.com
Received: from Unknown (HELO ecmme.com) (107.150.52.187) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 13 Oct 2019 23:21:42 +0000
Received: from ecmme.com (localhost [127.0.0.1])	by ecmme.com (8.14.4/8.14.4) with ESMTP id x9DNLdnk024257	for <glibc-bugs@sourceware.org>; Mon, 14 Oct 2019 02:21:39 +0300
Received: (from apache@localhost)	by ecmme.com (8.14.4/8.14.4/Submit) id x9DNLcYN024255;	Mon, 14 Oct 2019 02:21:38 +0300
Date: Sun, 13 Oct 2019 23:21:00 -0000
From: "Ray Creation" <info@ecmme.com>
To: glibc-bugs@sourceware.org
Reply-To: "Ray Creation" <info@ecmme.com>
Message-ID: <20191013094704.26272978@ecmme.com>
MIME-Version: 1.0
Subject: Let your brand shine with a customized promo display
Content-length: 1309
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-SW-Source: 2019-10/txt/msg00051.txt.bz2

 Email not displaying correctly? View it in your browser | Share it
 You are seeing this Email in Plain Text Version; Switch to HTML or Click this link http://dits.ws/a/44451 to View it properly.




 http://www.me-trk.com/url/u8nGvLduh5R6hJJpe5rMxMfAuXe2uHqEkq-6jJWlt5KnraKke8W0s729t5KGgHh-hQ== http://www.me-trk.com/url/u8nGvLduh5R6hJJpe5rKzMl6tqrNtse3rbiyw8GDwLG4boaZe8W0s729t5KGgHh-hQ==  info@raycreation.net  salesraycreation@gmail.com http://www.me-trk.com/url/u8nGvLduh5R6hJJpe5rKzMl6tqrNtse3rbiyw8GDwLG4boaZe8W0s729t5KGgHh-hQ== http://www.me-trk.com/url/u8nGvLduh5R6hJJpe5rKzMl6qqq3uLfBu693t8LCd36Ku7XMuMSxpb29wsO2tbe5wLTOxXF2j3rGvcHAra2Rh4mGgXU= http://www.me-trk.com/url/u8nGvLduh5R6hJJpe5rKzMl6rbfHx7a5vqW2grbEv3F2j8a0zrGvtq61x77BuqOtvcbFvq29vHmFm3i_rLjIvLmPgHh9iYQ= http://www.me-trk.com/url/u8nGvLduh5R6hJJpe5rKzMl6sLLCvrq2tbJ3t8LCd36KrMPAxbO6vW6GmcezxXGsxri2xrWzt3rGvcHAra2Rh4mGgXU= http://www.me-trk.com/url/u8nGvLduh5R6hJJpe5rKzMl6vbjJx8q0sXKsw8B6hJKnsbXBw7e4aXuaqJjJvbt7najJorp7rrytxoaEvIu9rb3Jcrexw8e-tol4fYiIhg== tel:+9613225080 tel:+96170469069

 Subscription Information:
 This email was sent to glibc-bugs@sourceware.org because you are Subscribed to Saudi Arabia List
 Click Here to permanently Unsubscribe from this List.

 Sent to you by:
 DIGITAL ITS | Tel: +961 5 464 323