https://sourceware.org/bugzilla/show_bug.cgi?id=24606 Bug ID: 24606 Summary: Dynamic TLS address is not congruent with p_align when (p_vaddr % p_align != 0) Product: glibc Version: 2.31 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: rprichard at google dot com CC: drepper.fsp at gmail dot com Target Milestone: --- For static TLS, glibc and musl allocate a TLS block such that p_vaddr and the run-time address are congruent with respect to p_align: (tpoffset % p_align) == (p_vaddr % p_align) For dynamic TLS, musl appears to satisfy the same formula, but glibc doesn't appear to. Is this considered a bug in glibc? For context, I'm working on ELF TLS in Android's Bionic libc, and a problem recently came up where a TLS overalignment hack in LLVM lld resulted in TLS segments where (p_vaddr % p_align) was non-zero. See https://bugs.llvm.org/show_bug.cgi?id=41527 and https://reviews.llvm.org/D61824. The lld hack has since been reverted, and lld will usually satisfy (p_vaddr % p_align == 0) again, unless 8KiB-or-larger TLS alignment is used. Test case (I have only tested this on x86-64): $ gcc -fpic -shared test1_dso.c -o libtest1_dso.so $ gcc test1_main.c -o test1 -ldl -Wl,-rpath,'$ORIGIN' $ gcc trim-pt-tls.c -o trim-pt-tls $ ./trim-pt-tls libtest1_dso.so $ ./test1 tp = 0x7f4bcfc34700 &tlsvar = 0x56124db2f9e0 tlsvar[1] = 7 $ readelf -lW libtest1_dso.so ... Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align ... TLS 0x000ded 0x0000000000200ded 0x0000000000200ded 0x000003 0x000003 R 0x4 ... (v_addr % p_align) is 1. Static linkers typically ensure that (v_addr % p_align) is 0 instead. musl appears to align the DTLS block at 1-mod-4 instead: tp = 0x7fa4faea6b48 &tlsvar = 0x7fa4faea72d1 tlsvar[1] = 7 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45532-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 03:56:33 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 92923 invoked by alias); 23 May 2019 03:56:32 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 92878 invoked by uid 48); 23 May 2019 03:56:29 -0000 From: "rprichard at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_align when (p_vaddr % p_align != 0) Date: Thu, 23 May 2019 03:56: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rprichard at google 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: attachments.created Message-ID: In-Reply-To: References: 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-05/txt/msg00162.txt.bz2 Content-length: 324 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 --- Comment #1 from Ryan Prichard --- Created attachment 11793 --> https://sourceware.org/bugzilla/attachment.cgi?id=11793&action=edit test case DSO -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45534-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 03:57:33 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 93816 invoked by alias); 23 May 2019 03:57:33 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 93769 invoked by uid 48); 23 May 2019 03:57:30 -0000 From: "rprichard at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_align when (p_vaddr % p_align != 0) Date: Thu, 23 May 2019 03:57: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rprichard at google 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: attachments.created Message-ID: In-Reply-To: References: 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-05/txt/msg00164.txt.bz2 Content-length: 324 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 --- Comment #3 from Ryan Prichard --- Created attachment 11795 --> https://sourceware.org/bugzilla/attachment.cgi?id=11795&action=edit trim-pt-tls.c -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45533-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 03:57:05 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 93425 invoked by alias); 23 May 2019 03:57:05 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 93388 invoked by uid 48); 23 May 2019 03:57:01 -0000 From: "rprichard at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_align when (p_vaddr % p_align != 0) Date: Thu, 23 May 2019 03:57: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rprichard at google 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: attachments.created Message-ID: In-Reply-To: References: 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-05/txt/msg00163.txt.bz2 Content-length: 323 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 --- Comment #2 from Ryan Prichard --- Created attachment 11794 --> https://sourceware.org/bugzilla/attachment.cgi?id=11794&action=edit test1_main.c -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45535-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 03:58:04 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 94319 invoked by alias); 23 May 2019 03:58:04 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 94271 invoked by uid 48); 23 May 2019 03:58:01 -0000 From: "rprichard at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_align when (p_vaddr % p_align != 0) Date: Thu, 23 May 2019 03:58: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rprichard at google 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: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: 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-05/txt/msg00165.txt.bz2 Content-length: 610 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 Ryan Prichard changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #11793|0 |1 is obsolete| | --- Comment #4 from Ryan Prichard --- Created attachment 11796 --> https://sourceware.org/bugzilla/attachment.cgi?id=11796&action=edit test1_dso.c -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45536-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 04:01:17 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 96466 invoked by alias); 23 May 2019 04:00:45 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 96168 invoked by uid 48); 23 May 2019 04:00:22 -0000 From: "rprichard at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_vaddr when (p_vaddr % p_align != 0) Date: Thu, 23 May 2019 04:00: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rprichard at google 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: short_desc Message-ID: In-Reply-To: References: 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-05/txt/msg00166.txt.bz2 Content-length: 556 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 Ryan Prichard changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Dynamic TLS address is not |Dynamic TLS address is not |congruent with p_align when |congruent with p_vaddr when |(p_vaddr % p_align != 0) |(p_vaddr % p_align != 0) -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45537-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 04:06:59 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 100515 invoked by alias); 23 May 2019 04:06:59 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 100475 invoked by uid 48); 23 May 2019 04:06:55 -0000 From: "rprichard at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_vaddr when (p_vaddr % p_align != 0) Date: Thu, 23 May 2019 04:06: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rprichard at google 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00167.txt.bz2 Content-length: 547 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 Ryan Prichard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugdal at aerifal dot cx, | |nsz at port70 dot net, | |rprichard at google dot com -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45538-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 04:31:23 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 125828 invoked by alias); 23 May 2019 04:31:14 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 125757 invoked by uid 48); 23 May 2019 04:31:10 -0000 From: "starke.nicholas at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] New: Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 04:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: starke.nicholas 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 target_milestone attachments.created Message-ID: 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-05/txt/msg00168.txt.bz2 Content-length: 4369 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 Bug ID: 24607 Summary: Segmentation Fault in Glob with invalid path Product: glibc Version: 2.29 Status: UNCONFIRMED Severity: normal Priority: P2 Component: glob Assignee: unassigned at sourceware dot org Reporter: starke.nicholas at gmail dot com Target Milestone: --- Created attachment 11798 --> https://sourceware.org/bugzilla/attachment.cgi?id=11798&action=edit Screenshot of Proof of Concept I noticed a segmentation fault as a result of fuzzing the PHP glob functions. I have provided the string below. No flags to glob were specified. This was tested against the PHP glob function as well as the glob.h glob function in c. This was tested against 2.27 and 2.29. Please let me know if you have any additional questions. This may be a security issue. String input: //*/.*//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////./.** -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45539-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 04:38:16 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 5434 invoked by alias); 23 May 2019 04:38:15 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 5402 invoked by uid 48); 23 May 2019 04:38:12 -0000 From: "rprichard at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_vaddr when (p_vaddr % p_align != 0) Date: Thu, 23 May 2019 04: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: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rprichard at google 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00169.txt.bz2 Content-length: 398 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 Ryan Prichard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maskray at google dot com -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45541-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 07:09:53 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 44476 invoked by alias); 23 May 2019 07:09:53 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 44444 invoked by uid 48); 23 May 2019 07:09:50 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug math/24603] sysdeps/ieee754/dbl-64/branred.c is slow when compiled with -O3 -march=skylake Date: Thu, 23 May 2019 07:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.31 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: In-Reply-To: References: 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-05/txt/msg00171.txt.bz2 Content-length: 456 https://sourceware.org/bugzilla/show_bug.cgi?id=24603 Florian Weimer 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-45540-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 07:09:25 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 37472 invoked by alias); 23 May 2019 07:09:24 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 33102 invoked by uid 48); 23 May 2019 07:09:21 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 07:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: WAITING 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_status cf_reconfirmed_on cc everconfirmed Message-ID: In-Reply-To: References: 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-05/txt/msg00170.txt.bz2 Content-length: 834 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2019-05-23 CC| |fweimer at redhat dot com Ever confirmed|0 |1 --- Comment #1 from Florian Weimer --- We need more details. The input string alone, with the GLOB_ONLYDIR | GLOB_MARK | GLOB_NOSORT flags argument (as shown in the screenshot—the 8198 argument) does not reproduce this. Thanks. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45542-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 07:10:01 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 44785 invoked by alias); 23 May 2019 07:10:01 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 44738 invoked by uid 48); 23 May 2019 07:09:58 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/24595] [2.28 Regression]: Deadlock in atfork handler which calls dlclose Date: Thu, 23 May 2019 07:10: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: 2.28 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: In-Reply-To: References: 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-05/txt/msg00172.txt.bz2 Content-length: 456 https://sourceware.org/bugzilla/show_bug.cgi?id=24595 Florian Weimer 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-45543-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 08:12:01 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 47795 invoked by alias); 23 May 2019 08:12:01 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 47745 invoked by uid 48); 23 May 2019 08:11:58 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/24166] Dl_serinfo.dls_serpath[1] in dlfcn.h causes UBSAN false positives, change to modern flexible array Date: Thu, 23 May 2019 08:12: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: 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: bug_status Message-ID: In-Reply-To: References: 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-05/txt/msg00173.txt.bz2 Content-length: 375 https://sourceware.org/bugzilla/show_bug.cgi?id=24166 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45544-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 08:15:49 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 87112 invoked by alias); 23 May 2019 08:15:48 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 87077 invoked by uid 48); 23 May 2019 08:15:45 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/24166] Dl_serinfo.dls_serpath[1] in dlfcn.h causes UBSAN false positives, change to modern flexible array Date: Thu, 23 May 2019 08:15: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: enhancement 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: In-Reply-To: References: 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-05/txt/msg00174.txt.bz2 Content-length: 464 https://sourceware.org/bugzilla/show_bug.cgi?id=24166 Florian Weimer 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-45545-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 09:50:41 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 62887 invoked by alias); 23 May 2019 09:50:41 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 62758 invoked by uid 55); 23 May 2019 09:50:38 -0000 From: "cvs-commit at gcc dot gnu.org" To: glibc-bugs@sourceware.org Subject: [Bug libc/18093] Corrupted aux-cache causes ldconfig to segfault Date: Thu, 23 May 2019 09: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: 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: 2.29 X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-05/txt/msg00175.txt.bz2 Content-length: 848 https://sourceware.org/bugzilla/show_bug.cgi?id=18093 --- Comment #6 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alexandra Hajkova : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=481c30cb9573a280649fbf27251e6a0f4af1b2b1 commit 481c30cb9573a280649fbf27251e6a0f4af1b2b1 Author: Alexandra H�jkov� Date: Thu May 9 13:51:40 2019 +0200 elf: Add tst-ldconfig-bad-aux-cache test [BZ #18093] This test corrupts /var/cache/ldconfig/aux-cache and executes ldconfig to check it will not segfault using the corrupted aux_cache. The test uses the test-in-container framework. Verified no regressions on x86_64. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45546-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 11:12:52 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 1316 invoked by alias); 23 May 2019 11:12:52 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 1284 invoked by uid 48); 23 May 2019 11:12:49 -0000 From: "sourceware at jonathancottrill dot net" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 11:12:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sourceware at jonathancottrill dot net X-Bugzilla-Status: WAITING 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00176.txt.bz2 Content-length: 469 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 Jonathan Cottrill changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sourceware@jonathancottrill | |.net -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45547-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 11:59:10 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 68363 invoked by alias); 23 May 2019 11:59:10 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 68324 invoked by uid 48); 23 May 2019 11:59:06 -0000 From: "sourceware at jonathancottrill dot net" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 11:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sourceware at jonathancottrill dot net X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00177.txt.bz2 Content-length: 4283 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 --- Comment #2 from Jonathan Cottrill --- I'm able to reproduce this in Ubuntu 19.04, glibc 2.29, inside a Docker container, using these steps: docker run --rm -it --privileged ubuntu:19.04 Inside the container: apt update && apt install -y gcc gdb cat >glob.c <<<' #include #include int main() { glob_t g; glob("//*/.*//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////./.**", 8198, NULL, &g); return 0; } ' gcc -o glob glob.c gdb -ex run glob Output is similar to screenshot Nicholas Starke posted: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7ec0984 in __glob (pattern=pattern@entry=0x7fffff7ff300 "//*/.*", '/' ..., flags=flags@entry=8198, errfunc=errfunc@entry=0x0, pglob=pglob@entry=0x7fffffffcfd0) at ../posix/glob.c:289 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45548-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 12:23:46 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 127027 invoked by alias); 23 May 2019 12:23:46 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 126969 invoked by uid 48); 23 May 2019 12:23:43 -0000 From: "schwab@linux-m68k.org" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 12:23:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00178.txt.bz2 Content-length: 238 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 --- Comment #3 from Andreas Schwab --- That is most likely a stack overflow. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45549-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 12:46:40 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 10177 invoked by alias); 23 May 2019 12:46:39 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 8574 invoked by uid 48); 23 May 2019 12:46:36 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 12:46:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org X-Bugzilla-Status: WAITING 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00179.txt.bz2 Content-length: 668 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 Adhemerval Zanella changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #4 from Adhemerval Zanella --- The tests passed with 'ulimit -s unlimited'. The pattern leads to recursive calls to __glob at glob.c:584. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45550-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 12:58:13 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 34033 invoked by alias); 23 May 2019 12:58:13 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 33985 invoked by uid 48); 23 May 2019 12:58:10 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 12:58:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00180.txt.bz2 Content-length: 295 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 --- Comment #5 from Florian Weimer --- Right. I suspect it's also related to file system contents whether it's triggered or not. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45551-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 14:49:40 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 123992 invoked by alias); 23 May 2019 14:49:40 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 123929 invoked by uid 48); 23 May 2019 14:49:37 -0000 From: "starke.nicholas at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 14:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: starke.nicholas at gmail dot com X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00181.txt.bz2 Content-length: 542 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 --- Comment #6 from Nicholas Starke --- Thank you to Jonathan Cottrill for the in-depth reproduction steps. This is nearly exactly how I triaged the initial crash. I apologize for not attaching the full proof of concept test harness for reproducing this. That's my mistake. What sort of information do you need at this point? How can I help in your assessment? -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45552-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 15:03:56 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 100693 invoked by alias); 23 May 2019 15:03:55 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 100616 invoked by uid 48); 23 May 2019 15:03:49 -0000 From: "sjon at hortensius dot net" To: glibc-bugs@sourceware.org Subject: [Bug time/24614] New: nl_NL LC_MONETARY doesn't match CLDR 27 Date: Thu, 23 May 2019 15:03: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: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sjon at hortensius dot net 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 target_milestone Message-ID: 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-05/txt/msg00182.txt.bz2 Content-length: 792 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 Bug ID: 24614 Summary: nl_NL LC_MONETARY doesn't match CLDR 27 Product: glibc Version: 2.31 Status: UNCONFIRMED Severity: normal Priority: P2 Component: time Assignee: unassigned at sourceware dot org Reporter: sjon at hortensius dot net Target Milestone: --- This was originally reported as https://bugs.php.net/bug.php?id=78056 CLDR Version 27.0.1 defines "¤ -#,##0.00" as standard-currency formatting for nl_NL - however the current ./localedata/locales/nl_NL has n_sign_posn=2 which I think should be updated to n_sign_posn=4 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45553-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 15:41:27 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 51082 invoked by alias); 23 May 2019 15:41:27 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 51037 invoked by uid 48); 23 May 2019 15:41:24 -0000 From: "wesley at weha dot be" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24615] New: nl_BE and probably nl_NL as well gives the wrong money format with negative numbers Date: Thu, 23 May 2019 15:41:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wesley at weha dot be 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: 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-05/txt/msg00183.txt.bz2 Content-length: 985 https://sourceware.org/bugzilla/show_bug.cgi?id=24615 Bug ID: 24615 Summary: nl_BE and probably nl_NL as well gives the wrong money format with negative numbers Product: glibc Version: unspecified Status: UNCONFIRMED Severity: normal Priority: P2 Component: localedata Assignee: unassigned at sourceware dot org Reporter: wesley at weha dot be CC: libc-locales at sourceware dot org Target Milestone: --- I posted a bug on PHP.net because the money_format was wrong for nl_BE when using a negative value. Apparently this links back to glibc: https://bugs.php.net/bug.php?id=78056&edit=2 So -1234.56 comes out as € 1 234,56- which should actually be € -1 234,56 Documentation: https://taaladvies.net/taal/advies/vraag/1198/euro_12_12/ -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45554-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 15:45:30 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 91359 invoked by alias); 23 May 2019 15:45:30 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 89435 invoked by uid 48); 23 May 2019 15:45:27 -0000 From: "wesley at weha dot be" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24615] nl_BE and probably nl_NL as well gives the wrong money format with negative numbers Date: Thu, 23 May 2019 15:45: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wesley at weha dot be X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE 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: In-Reply-To: References: 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-05/txt/msg00184.txt.bz2 Content-length: 574 https://sourceware.org/bugzilla/show_bug.cgi?id=24615 Wesley changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Wesley --- Already posted apparently :) *** This bug has been marked as a duplicate of bug 24614 *** -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45555-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 15:45:30 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 91619 invoked by alias); 23 May 2019 15:45:30 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 89808 invoked by uid 48); 23 May 2019 15:45:27 -0000 From: "wesley at weha dot be" To: glibc-bugs@sourceware.org Subject: [Bug time/24614] nl_NL LC_MONETARY doesn't match CLDR 27 Date: Thu, 23 May 2019 15:45: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: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wesley at weha dot be 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00185.txt.bz2 Content-length: 499 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 Wesley changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wesley at weha dot be --- Comment #1 from Wesley --- *** Bug 24615 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45556-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 15:49:30 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 13459 invoked by alias); 23 May 2019 15:49:29 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 13376 invoked by uid 48); 23 May 2019 15:49:26 -0000 From: "schwab@linux-m68k.org" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 27 Date: Thu, 23 May 2019 15:49: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.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org 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 version Message-ID: In-Reply-To: References: 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-05/txt/msg00186.txt.bz2 Content-length: 518 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |libc-locales at sourceware dot org Component|time |localedata Version|2.31 |2.29 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45557-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 16:12:17 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 72116 invoked by alias); 23 May 2019 16:12:17 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 72035 invoked by uid 48); 23 May 2019 16:12:14 -0000 From: "nsz at gcc dot gnu.org" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_vaddr when (p_vaddr % p_align != 0) Date: Thu, 23 May 2019 16:12: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nsz at gcc dot gnu.org 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00187.txt.bz2 Content-length: 991 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 Szabolcs Nagy changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nsz at gcc dot gnu.org --- Comment #5 from Szabolcs Nagy --- i think the intention in glibc is to satisfy the % formula, based on the big comment in _dl_determine_tlsoffset (and on the presence of map->l_tls_firstbyte_offset which is the % p_align remainder). it seems to work on aarch64, at least the test gives &tlsvar % 4 == 1. x86 tls offsets are handled with a different code path because that's "tls variant 2" (TLS_TCB_AT_TP) instead of "tls variant 1" (TLS_DTV_AT_TP) so it's possible that there is a bug in that (but right now i dont have an x86 machine available to test that). -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45558-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 17:52:19 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 122849 invoked by alias); 23 May 2019 17:52:19 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 122788 invoked by uid 48); 23 May 2019 17:52:15 -0000 From: "wdijkstr at arm dot com" To: glibc-bugs@sourceware.org Subject: =?UTF-8?B?W0J1ZyBidWlsZC8yNDU1Nl0gW0dDQyA5XSBlcnJvcjog4oCYJXPigJkgZGly?= =?UTF-8?B?ZWN0aXZlIGFyZ3VtZW50IGlzIG51bGwgWy1XZXJyb3I9Zm9ybWF0LW92ZXJm?= =?UTF-8?B?bG93PV0=?Date: Thu, 23 May 2019 17:52: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: 2.30 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wdijkstr at arm 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: cc Message-ID: In-Reply-To: References: 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-05/txt/msg00188.txt.bz2 Content-length: 1201 https://sourceware.org/bugzilla/show_bug.cgi?id=24556 Wilco changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wdijkstr at arm dot com --- Comment #1 from Wilco --- > do_one_test (impl, s1, s2, fail ? NULL : s1 + len1 - len2); >grep "do_one_test.*NULL" -R * benchtests/bench-strstr.c: do_one_test (impl, s1, s2, fail ? NULL : s1 + len1 - len2); benchtests/bench-strstr.c: do_one_test (impl, hs, ne, NULL); benchtests/bench-strstr.c: do_one_test (impl, hs, ne, NULL); benchtests/bench-strstr.c: do_one_test (impl, hs, ne, NULL); benchtests/bench-strcasestr.c: do_one_test (impl, s1, s2, fail ? NULL : s1 + len1 - len2); string/test-strstr.c: do_one_test (impl, s1, s2, fail ? NULL : s1 + len1 - len2); string/test-strcasestr.c: do_one_test (impl, s1, s2, fail ? NULL : s1 + len1 - len2); There are many more tests/benchmarks which pass NULL, eg. any string function which can return NULL. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45559-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 18:15:43 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 65372 invoked by alias); 23 May 2019 18:15:40 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 65223 invoked by uid 48); 23 May 2019 18:15:24 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 18:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00189.txt.bz2 Content-length: 1092 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 --- Comment #7 from Adhemerval Zanella --- (In reply to Nicholas Starke from comment #6) > Thank you to Jonathan Cottrill for the in-depth reproduction steps. This is > nearly exactly how I triaged the initial crash. > > I apologize for not attaching the full proof of concept test harness for > reproducing this. That's my mistake. > > What sort of information do you need at this point? How can I help in your > assessment? My understanding is it works as intended. The pattern triggers a recursive call on glob implementation, where when glob sees 'pattern/' it expands 'pattern' by calling. The valgring massif tool shows a peak usage of 9,606,960 bytes for this testcase and usually, distro sets the default limit of stack to around 8MB. To lower the glob stack usage it would require a complete refactor to save/restore the state in a heap-allocated variable and remove the recursion. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45560-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 18:21:34 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 69868 invoked by alias); 23 May 2019 18:21:34 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 69763 invoked by uid 48); 23 May 2019 18:21:31 -0000 From: "starke.nicholas at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 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: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: starke.nicholas at gmail dot com X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00190.txt.bz2 Content-length: 259 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 --- Comment #8 from Nicholas Starke --- I apologize if this was a total waste of time. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45561-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 18:34:21 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 44684 invoked by alias); 23 May 2019 18:34:20 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 42917 invoked by uid 48); 23 May 2019 18:34:18 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 18:34:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00191.txt.bz2 Content-length: 391 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 --- Comment #9 from Adhemerval Zanella --- (In reply to Nicholas Starke from comment #8) > I apologize if this was a total waste of time. No worries, if it is ok to you I will close this bug report as not a bug. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45562-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 18:36:33 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 56445 invoked by alias); 23 May 2019 18:36:32 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 56390 invoked by uid 48); 23 May 2019 18:36:29 -0000 From: "starke.nicholas at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 18:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: starke.nicholas at gmail dot com X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00192.txt.bz2 Content-length: 266 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 --- Comment #10 from Nicholas Starke --- Thank you, I am fine with closing this as not a bug. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45563-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 18:38:13 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 57817 invoked by alias); 23 May 2019 18:38:12 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 57763 invoked by uid 48); 23 May 2019 18:38:09 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug glob/24607] Segmentation Fault in Glob with invalid path Date: Thu, 23 May 2019 18:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: glob X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot 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: In-Reply-To: References: 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-05/txt/msg00193.txt.bz2 Content-length: 564 https://sourceware.org/bugzilla/show_bug.cgi?id=24607 Adhemerval Zanella changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |INVALID --- Comment #11 from Adhemerval Zanella --- As per previous comments. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45564-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 19:31:45 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 45583 invoked by alias); 23 May 2019 19:31:45 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 45555 invoked by uid 48); 23 May 2019 19:31:41 -0000 From: "eggert at cs dot ucla.edu" To: glibc-bugs@sourceware.org Subject: [Bug stdio/24616] New: Document undefined behavior of printf ("%s", NULL) Date: Thu, 23 May 2019 19:31:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: stdio X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: eggert at cs dot ucla.edu 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 attachments.created Message-ID: 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-05/txt/msg00194.txt.bz2 Content-length: 1294 https://sourceware.org/bugzilla/show_bug.cgi?id=24616 Bug ID: 24616 Summary: Document undefined behavior of printf ("%s", NULL) Product: glibc Version: 2.29 Status: NEW Severity: normal Priority: P2 Component: stdio Assignee: unassigned at sourceware dot org Reporter: eggert at cs dot ucla.edu Target Milestone: --- Created attachment 11801 --> https://sourceware.org/bugzilla/attachment.cgi?id=11801&action=edit Patch to document printf ("%s", NULL) to be undefined Although the glibc manual documents printf ("%s", NULL) as outputting "(null)", in practice GCC and other compilers now sometimes optimize away calls to printf and these optimizations rely on printf ("%s", NULL) having undefined behavior. The glibc manual should be changed to document what happens from the user's point of view, as opposed to documenting what we might like to happen. Similarly, the test cases should not attempt to test undefined behavior. Proposed patch attached. This patch was inspired by this thread on libc-alpha: https://sourceware.org/ml/libc-alpha/2019-05/msg00539.html Also see bug#5618. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45565-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 23 20:38:53 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 111916 invoked by alias); 23 May 2019 20:38:53 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 111846 invoked by uid 48); 23 May 2019 20:38:49 -0000 From: "rprichard at google dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_vaddr when (p_vaddr % p_align != 0) Date: Thu, 23 May 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: 2.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rprichard at google 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: In-Reply-To: References: 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-05/txt/msg00195.txt.bz2 Content-length: 819 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 --- Comment #6 from Ryan Prichard --- I see the same thing with aarch64 glibc: tp = 0x77f7144710 &tlsvar = 0x77f71447b1 Based on the value of &tlsvar vs __builtin_thread_pointer(), it appears that a small-enough TLS segment is automatically allocated in reserved static TLS space. If I increase the size of tlsvar from 4 to 0x1000, then the test case fails: tp = 0x771d65b710 &tlsvar = 0x64be7458e0 On x86-64, if I mark tlsvar with __attribute__((tls_model("initial-exec"))), forcing it into the reserved static TLS area, then the test case passes: tp = 0x7f6033d7c700 &tlsvar = 0x7f6033d7c685 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45566-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri May 24 09:26:57 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 121418 invoked by alias); 24 May 2019 09:26:57 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 121022 invoked by uid 48); 24 May 2019 09:26:52 -0000 From: "nsz at gcc dot gnu.org" To: glibc-bugs@sourceware.org Subject: [Bug libc/24606] Dynamic TLS address is not congruent with p_vaddr when (p_vaddr % p_align != 0) Date: Fri, 24 May 2019 09:26: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: nsz 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_status cf_reconfirmed_on everconfirmed Message-ID: In-Reply-To: References: 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-05/txt/msg00196.txt.bz2 Content-length: 1412 https://sourceware.org/bugzilla/show_bug.cgi?id=24606 Szabolcs Nagy changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2019-05-24 Ever confirmed|0 |1 --- Comment #7 from Szabolcs Nagy --- sorry somehow i missed that we are talking about dynamic tls and i was looking at the static tls code. indeed the dynamic tls code does not access the l_tls_firstbyte_offset, only alignment and size are passed to allocate_dtv_entry. i guess there were historical linkers that produced p_vaddr % p_align != 0 for static tls, but not for dynamic tls or the dynamic tls case were not visible because affected targets supported unaligned access, so it was only fixed in the static tls case. (with local exec tls the runtime tp offset must match the value computed by the static linker, there is no such requirement in the dynamic case, so if the user code does not care about alignment then wrong alignment works.) i assume nowadays linkers ensure the beginning of the tls block is aligned, so it's not an issue in practice, but still an ELF TLS correctness issue. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45567-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri May 24 18:03:25 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 5731 invoked by alias); 24 May 2019 18:03:25 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 5686 invoked by uid 48); 24 May 2019 18:03:21 -0000 From: "yann at droneaud dot fr" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/24561] _dl_addr: linear lookup inefficient, making mtrace() feature very slow Date: Fri, 24 May 2019 18: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.31 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yann at droneaud dot fr 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00197.txt.bz2 Content-length: 586 https://sourceware.org/bugzilla/show_bug.cgi?id=24561 --- Comment #5 from Yann Droneaud --- (In reply to Florian Weimer from comment #4) > Sorry, this came across wrong. If someone else has a patch for this, I'll > gladly review it. OK, I'm investigating. While trying to build a test case that exhibit the issue I've made an over-engineered tool to generate shared libraries: https://github.com/opteya/dladdr-test I can now make a smaller reproducer. And start debugging. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45568-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri May 24 19:14:40 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 117787 invoked by alias); 24 May 2019 19:14:40 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 117705 invoked by uid 48); 24 May 2019 19:14:35 -0000 From: "mgulick at mathworks dot com" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/19329] dl-tls.c assert failure at concurrent pthread_create and dlopen Date: Fri, 24 May 2019 19:14: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.22 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mgulick at mathworks dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: nszabolcs at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: 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-05/txt/msg00198.txt.bz2 Content-length: 751 https://sourceware.org/bugzilla/show_bug.cgi?id=19329 Mike Gulick changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mgulick at mathworks dot com --- Comment #14 from Mike Gulick --- Just want to add that the two patches posted here (and the off-by-one fix in the comments) have been running by my employer (MathWorks) on at least 1000 Debian 9 systems for the past 6 months without issue. It would be great if these patches could be accepted into glibc itself. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45569-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri May 24 19:46:52 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 121347 invoked by alias); 24 May 2019 19:46:52 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 121255 invoked by uid 48); 24 May 2019 19:46:49 -0000 From: "carlos at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/19329] dl-tls.c assert failure at concurrent pthread_create and dlopen Date: Fri, 24 May 2019 19: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.22 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: nszabolcs at gmail dot com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-05/txt/msg00199.txt.bz2 Content-length: 975 https://sourceware.org/bugzilla/show_bug.cgi?id=19329 --- Comment #15 from Carlos O'Donell --- (In reply to Mike Gulick from comment #14) > Just want to add that the two patches posted here (and the off-by-one fix in > the comments) have been running by my employer (MathWorks) on at least 1000 > Debian 9 systems for the past 6 months without issue. It would be great if > these patches could be accepted into glibc itself. None of these changes are easy to integrate because they fail to explain in detailed notes why they are correct. We take the conservative approach not to apply complete solutions. Someone seeing this problem has to take the position to champion the broader solution as positioned by Szabolcs from Arm. Alternatively someone needs to explain why the partial solution is better than no solution and champion that on libc-alpha. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45570-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri May 24 21:43:51 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 56726 invoked by alias); 24 May 2019 21:43:51 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 56621 invoked by uid 48); 24 May 2019 21:43:46 -0000 From: "digitalfreak at lingonborough dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24580] Appropriate AM/PM time representation for en_NG Date: Fri, 24 May 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: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: digitalfreak at lingonborough 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: In-Reply-To: References: 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-05/txt/msg00200.txt.bz2 Content-length: 1579 https://sourceware.org/bugzilla/show_bug.cgi?id=24580 Rafal Luzynski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |digitalfreak@lingonborough. | |com --- Comment #1 from Rafal Luzynski --- Thank you for filing this bug report and the patch. Please note that, as the current comment says, t_fmt_ampm should remain empty unless 12-hour clock is actually used in that locale. Our authoritative source is CLDR. en_NG is supported but it is highly incomplete. [1] The part which is our source for time formats is called "Formats - Standard - Time Formats". If you look at other Nigerian locales in CLDR like ha_NG [2] or ig_NG [3] or yo_NG [4] they also suggest that the typical time format is 24-hour. On the other hand, these locales in glibc use 12-hour format in t_fmt_ampm. Please explain who is wrong here. If CLDR is wrong then we should file a ticket in CLDR. We need some official (scientific, government, etc.) sources to convince CLDR. Also, you need am_pm field if you want to use t_fmt_ampm. [1] http://st.unicode.org/cldr-apps/v#/en_NG/Gregorian/ [2] http://st.unicode.org/cldr-apps/v#/ha/Gregorian/ [3] http://st.unicode.org/cldr-apps/v#/ig/Gregorian/ [4] http://st.unicode.org/cldr-apps/v#/yo/Gregorian/ -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45571-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri May 24 22:47:37 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 92177 invoked by alias); 24 May 2019 22:47:36 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 92041 invoked by uid 48); 24 May 2019 22:47:33 -0000 From: "digitalfreak at lingonborough dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 27 Date: Fri, 24 May 2019 22: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.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: digitalfreak at lingonborough 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00201.txt.bz2 Content-length: 1229 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 Rafal Luzynski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |digitalfreak@lingonborough. | |com --- Comment #2 from Rafal Luzynski --- Thank you for the report. I am currently working on this bug. Please explain, what is the current grouping (thousands) separator for nl_NL? CLDR [1] says it is a single dot (".") and bug 23831 says the same which is consistent. But the link you quoted [2] and bug 24615 say it should be space. Also the current value of mon_thousands_sep (but not thousands_sep) is (narrow no-break space). I lean to assume that the correct value is a dot but the other bugs quote the space because they were about the minus sign position and ignored the thousands separator. [1] http://st.unicode.org/cldr-apps/v#/nl/Symbols/ [2] https://bugs.php.net/bug.php?id=78056 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45572-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri May 24 23:01:19 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 103959 invoked by alias); 24 May 2019 23:01:18 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 103877 invoked by uid 48); 24 May 2019 23:01:15 -0000 From: "gentoo-bugzilla at jdrake dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/24595] [2.28 Regression]: Deadlock in atfork handler which calls dlclose Date: Fri, 24 May 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: nptl X-Bugzilla-Version: 2.28 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gentoo-bugzilla at jdrake 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00202.txt.bz2 Content-length: 1113 https://sourceware.org/bugzilla/show_bug.cgi?id=24595 --- Comment #5 from Jeremy Drake --- I did some playing in a test chroot with the test code and patch you provided. I modified the test case to call dlclose in the child handler, since that is what I saw happening, and added a waitpid call in the parent case (else on the pid == 0 if after the fork). Your proposed patch seems to do the trick there. I upgraded to sys-libs/glibc-2.29-r2 (which contains 669ff911e2571f74a2668493e326ac9a505776bd) and dev-libs/opensc-0.19.0-r2 on the real system I was having this issue on, and was surprised to see the hang/deadlock had gone away. One of the first things I found when I idenitifed this problem was that 669ff911 commit, and I attempted applying that as a patch and it did not solve the problem. Either I screwed that up, or the opensc change did something too. I am considering downgrading opensc back to 0.18.0 to attempt to determine which of these are the case. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45573-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat May 25 01:02:36 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 16891 invoked by alias); 25 May 2019 01:02:35 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 16835 invoked by uid 48); 25 May 2019 01:02:32 -0000 From: "gentoo-bugzilla at jdrake dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/24595] [2.28 Regression]: Deadlock in atfork handler which calls dlclose Date: Sat, 25 May 2019 01:02: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: 2.28 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gentoo-bugzilla at jdrake 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00203.txt.bz2 Content-length: 396 https://sourceware.org/bugzilla/show_bug.cgi?id=24595 --- Comment #6 from Jeremy Drake --- I downgraded opensc to 0.18.0 and the hang/deadlock is back. I also confirmed that there was a second thread in the parent. So I can test the patch in the real scenario after all. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45574-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat May 25 05:23:23 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 79256 invoked by alias); 25 May 2019 05:23:22 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 79205 invoked by uid 48); 25 May 2019 05:23:19 -0000 From: "wesley at weha dot be" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 27 Date: Sat, 25 May 2019 05:23: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.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wesley at weha dot be 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: In-Reply-To: References: 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-05/txt/msg00204.txt.bz2 Content-length: 551 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 --- Comment #3 from Wesley --- Oh, I didn't see he specified nl_NL. nl_BE should be like this: € -1 234,56 According to this guy: https://sourceware.org/bugzilla/show_bug.cgi?id=23831 nl_NL should be like this € -1.234,56 I'm from Belgium, not the Netherlands so I can't speak for them. In Belgium, both are correct, but the space is specified in the ISO/BIN norms. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45575-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat May 25 06:04:52 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 114737 invoked by alias); 25 May 2019 06:04:52 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 114698 invoked by uid 48); 25 May 2019 06:04:49 -0000 From: "agner at agner dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/13881] powl inaccurate for x86/x86_64 Date: Sat, 25 May 2019 06:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.15 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: agner at agner dot 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: cc attachments.created Message-ID: In-Reply-To: References: 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-05/txt/msg00205.txt.bz2 Content-length: 605 https://sourceware.org/bugzilla/show_bug.cgi?id=13881 agner at agner dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |agner at agner dot org --- Comment #4 from agner at agner dot org --- Created attachment 11802 --> https://sourceware.org/bugzilla/attachment.cgi?id=11802&action=edit Test case for powl accuracy -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45576-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat May 25 06:07:40 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 116505 invoked by alias); 25 May 2019 06:07:39 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 116467 invoked by uid 48); 25 May 2019 06:07:36 -0000 From: "agner at agner dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/13881] powl inaccurate for x86/x86_64 Date: Sat, 25 May 2019 06:07:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.15 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: agner at agner dot 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: In-Reply-To: References: 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-05/txt/msg00206.txt.bz2 Content-length: 543 https://sourceware.org/bugzilla/show_bug.cgi?id=13881 --- Comment #5 from agner at agner dot org --- Please reopen. powl is still less accurate than pow in version 2.27 (both gcc and clang). The attached test case powl.cpp has powl 5 times more inaccurate than pow. I have seen worse cases, but I have chosen a test case where it is easy to calculate the correct value. I have not seen any case where powl is more accurate than pow. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45577-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat May 25 07:28:13 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 85622 invoked by alias); 25 May 2019 07:28:12 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 85586 invoked by uid 48); 25 May 2019 07:28:09 -0000 From: "agner at agner dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/13881] powl inaccurate for x86/x86_64 Date: Sat, 25 May 2019 07:28:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.15 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: agner at agner dot 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: In-Reply-To: References: 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-05/txt/msg00207.txt.bz2 Content-length: 688 https://sourceware.org/bugzilla/show_bug.cgi?id=13881 --- Comment #6 from agner at agner dot org --- Some more test cases: powl(9.4401197044207130E-01,9.0396338480980503E+03) relative error 7.9E-13 powl(9.6205229632635447E-01,9.0396338480980503E+03) relative error 5.1E-13 powl(1.0567906354279399E+00,9.0396338480980503E+03) relative error 5.7E-13 powl(9.5952957579581444E-01,-1.6994966845030955E+04) relative error 1.8E-12 powl(9.4249308583367331E-01,5.1811882606772378E+03) relative error 6.4E-13 powl(1.0537202715568794E+00,5.1811882606772378E+03) relative error 4.2E-13 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45578-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat May 25 09:41:35 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 8411 invoked by alias); 25 May 2019 09:41:35 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 7799 invoked by uid 55); 25 May 2019 09:41:30 -0000 From: "keld at keldix dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 27 Date: Sat, 25 May 2019 09:41: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.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: keld at keldix 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: In-Reply-To: References: 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-05/txt/msg00208.txt.bz2 Content-length: 1142 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 --- Comment #4 from keld at keldix dot com --- banks in continental Europe thed to use . as mon_thousands_sep while for thousands_sep the customary separator is some kind of space. I am unhqppy about the space separator, as it makes it much harder to parse and not my impression of the conventions in scientific computing. keld On Sat, May 25, 2019 at 05:23:19AM +0000, wesley at weha dot be wrote: > https://sourceware.org/bugzilla/show_bug.cgi?id=24614 > > --- Comment #3 from Wesley --- > Oh, I didn't see he specified nl_NL. > nl_BE should be like this: ??? -1 234,56 > > According to this guy: https://sourceware.org/bugzilla/show_bug.cgi?id=23831 > nl_NL should be like this ??? -1.234,56 > > I'm from Belgium, not the Netherlands so I can't speak for them. > In Belgium, both are correct, but the space is specified in the ISO/BIN norms. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45579-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat May 25 09:54:20 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 96341 invoked by alias); 25 May 2019 09:54:20 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 96278 invoked by uid 48); 25 May 2019 09:54:16 -0000 From: "sjon at hortensius dot net" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 27 Date: Sat, 25 May 2019 09:54: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.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sjon at hortensius dot net 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: In-Reply-To: References: 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-05/txt/msg00209.txt.bz2 Content-length: 619 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 --- Comment #5 from sjon at hortensius dot net --- Currently nl_BE is (as for LC_MONETARY) an alias for nl_NL which is correct IMO. It seems there isn't a strict consensus as to what is correct for the thousand-separator - and I'd suggest keeping that discussion in #23831. Personally I agree with what's written in https://taaladvies.net/taal/advies/vraag/1/10000000_10_000_000/ - which basically says the space is ISO/BIN correct but the dot is more commonly used instead. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45580-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sat May 25 15:11:19 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 65712 invoked by alias); 25 May 2019 15:11:19 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 65652 invoked by uid 48); 25 May 2019 15:11:16 -0000 From: "wesley at weha dot be" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 27 Date: Sat, 25 May 2019 15:11: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.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: wesley at weha dot be 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: In-Reply-To: References: 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-05/txt/msg00210.txt.bz2 Content-length: 482 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 --- Comment #6 from Wesley --- Like I said, both are technically correct. I believe space is more commonly used, I never see dots as a separator. I care less about the thousand separator and more about the negative sign. Dots are easily removed, setting the negative sign after the euro and before the amount is harder. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45581-listarch-glibc-bugs=sources.redhat.com@sourceware.org Sun May 26 12:38:13 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 52293 invoked by alias); 26 May 2019 12:38:13 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 52227 invoked by uid 48); 26 May 2019 12:38:10 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug math/13881] powl inaccurate for x86/x86_64 Date: Sun, 26 May 2019 12:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.15 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: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: 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-05/txt/msg00211.txt.bz2 Content-length: 924 https://sourceware.org/bugzilla/show_bug.cgi?id=13881 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com --- Comment #7 from Florian Weimer --- (In reply to agner@agner.org from comment #5) > Please reopen. > > powl is still less accurate than pow in version 2.27 (both gcc and clang). > > The attached test case powl.cpp has powl 5 times more inaccurate than pow. I > have seen worse cases, but I have chosen a test case where it is easy to > calculate the correct value. I have not seen any case where powl is more > accurate than pow. Would you please file a separate bug for that? Thanks. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45582-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 00:22:49 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 42828 invoked by alias); 27 May 2019 00:22:48 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 42718 invoked by uid 48); 27 May 2019 00:22:37 -0000 From: "howaboutsynergy at pm dot me" To: glibc-bugs@sourceware.org Subject: [Bug stdio/24621] New: interleaved output in certain cases (especially when buffersize is less than 128 bytes) when multiple processes fprintf to a file fopen-ed in append mode Date: Mon, 27 May 2019 00:22:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: stdio X-Bugzilla-Version: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: howaboutsynergy at pm dot me 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 target_milestone attachments.created Message-ID: 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-05/txt/msg00212.txt.bz2 Content-length: 39756 https://sourceware.org/bugzilla/show_bug.cgi?id=24621 Bug ID: 24621 Summary: interleaved output in certain cases (especially when buffersize is less than 128 bytes) when multiple processes fprintf to a file fopen-ed in append mode Product: glibc Version: 2.29 Status: UNCONFIRMED Severity: normal Priority: P2 Component: stdio Assignee: unassigned at sourceware dot org Reporter: howaboutsynergy at pm dot me Target Milestone: --- Created attachment 11803 --> https://sourceware.org/bugzilla/attachment.cgi?id=11803&action=edit source code for ./runtests(script) and the .c file it's using I'm experiencing interleaving of output when multiple concurrent processes append(fopen(..,"a")) to the same file, when buffersize(given to setvbuf) is less than 128 bytes, even when using _IOLBF, even though buffer size is bigger than fprintf size. Relevant glibc file is `libio/fileops.c`, line `do_write = to_do - (block_size >= 128 ? to_do % block_size : 0);` There are other cases(like when fflush() is done after each line) in which interleaving probably shouldn't happen, seen in the below output. In the below `./runtests` output(source codes attached), setbufline=0 means there's no setvbuf() line executed setbufline=1 means I've used _IOFBF aka fully buffered setbufline=2 means I've used _IOLBF aka line buffering setbufline=3 and =4 means I've used _IONBF aka unbuffered setbufline=5 to be ignored here, but it should be the same as =1, except in this particular case here: https://stackoverflow.com/review/suggested-edits/23064119 which I haven't addressed below. fflusheachline=1 means there's an explicit fflush(f) after the fprintf(f,...); ignore howmany= (it's just fprintfsize minus 21) ``` /home/user/sandbox/c/interleaving_output $ ./runtests Bad, interleaving detected! buffersize=10 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=10 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=10 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=10 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=10 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=10 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=100 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=100 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=100 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=100 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=100 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=100 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=127 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=127 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=127 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=127 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=127 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=127 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=128 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=128 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=128 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=129 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=129 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=129 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=140 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=140 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=140 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=50 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=50 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=50 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=50 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=50 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=50 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=51 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=51 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=51 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=51 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=51 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=51 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=52 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=52 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=52 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=52 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=52 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=52 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=500 fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=500 fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=500 fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=BUFSIZ fprintfsize=51 fflusheachline=0 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=BUFSIZ fprintfsize=51 fflusheachline=0 setbufline=1 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=0 setbufline=2 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=0 setbufline=3 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=0 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=BUFSIZ fprintfsize=51 fflusheachline=0 setbufline=5 howmany=30 Bad, interleaving detected! buffersize=10 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=10 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=10 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=10 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=10 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=10 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=100 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=100 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=100 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=100 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=100 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=100 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=127 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=127 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=127 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=127 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=127 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=127 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=128 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=128 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=128 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=128 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=128 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=128 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=140 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=140 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=140 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=130 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=130 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=130 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=130 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=130 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=130 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=131 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=132 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=132 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=132 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=500 fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=500 fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=500 fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 Bad, interleaving detected! buffersize=BUFSIZ fprintfsize=131 fflusheachline=0 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=BUFSIZ fprintfsize=131 fflusheachline=0 setbufline=1 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=0 setbufline=2 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=0 setbufline=3 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=0 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=BUFSIZ fprintfsize=131 fflusheachline=0 setbufline=5 howmany=110 All good, no interleaving! buffersize=10 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=10 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=10 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=10 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=10 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=10 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=100 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=100 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=100 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=100 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=100 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=100 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=127 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=127 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=127 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=127 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=127 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=127 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 All good, no interleaving! buffersize=128 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 All good, no interleaving! buffersize=129 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 All good, no interleaving! buffersize=140 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=50 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=50 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=50 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=50 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=50 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=50 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=51 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=51 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=51 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=51 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=51 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=51 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=52 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=52 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=52 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=52 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=52 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=52 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 Bad, interleaving detected! buffersize=49 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 All good, no interleaving! buffersize=500 fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=1 setbufline=0 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=1 setbufline=1 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=1 setbufline=2 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=1 setbufline=3 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=1 setbufline=4 howmany=30 All good, no interleaving! buffersize=BUFSIZ fprintfsize=51 fflusheachline=1 setbufline=5 howmany=30 All good, no interleaving! buffersize=10 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=10 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=10 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=10 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=10 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=10 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=100 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=100 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=100 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=100 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=100 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=100 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=127 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=127 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=127 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=127 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=127 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=127 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=128 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=128 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=128 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=128 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=128 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=128 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 All good, no interleaving! buffersize=140 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=130 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=130 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=130 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=130 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=130 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=130 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 All good, no interleaving! buffersize=131 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 All good, no interleaving! buffersize=132 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 Bad, interleaving detected! buffersize=129 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 All good, no interleaving! buffersize=500 fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=1 setbufline=0 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=1 setbufline=1 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=1 setbufline=2 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=1 setbufline=3 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=1 setbufline=4 howmany=110 All good, no interleaving! buffersize=BUFSIZ fprintfsize=131 fflusheachline=1 setbufline=5 howmany=110 !! 140/312 tests failed real 0m36.521s user 0m30.571s sys 1m4.842s ``` glibc's relevant function: ```c size_t _IO_new_file_xsputn (FILE *f, const void *data, size_t n) { const char *s = (const char *) data; size_t to_do = n; int must_flush = 0; size_t count = 0; if (n <= 0) return 0; /* This is an optimized implementation. If the amount to be written straddles a block boundary (or the filebuf is unbuffered), use sys_write directly. */ /* First figure out how much space is available in the buffer. */ if ((f->_flags & _IO_LINE_BUF) && (f->_flags & _IO_CURRENTLY_PUTTING)) { count = f->_IO_buf_end - f->_IO_write_ptr; if (count >= n) { const char *p; for (p = s + n; p > s; ) { if (*--p == '\n') { count = p - s + 1; must_flush = 1; break; } } } } else if (f->_IO_write_end > f->_IO_write_ptr) count = f->_IO_write_end - f->_IO_write_ptr; /* Space available. */ /* Then fill the buffer. */ if (count > 0) { if (count > to_do) count = to_do; f->_IO_write_ptr = __mempcpy (f->_IO_write_ptr, s, count); s += count; to_do -= count; } if (to_do + must_flush > 0) { size_t block_size, do_write; /* Next flush the (full) buffer. */ if (_IO_OVERFLOW (f, EOF) == EOF) /* If nothing else has to be written we must not signal the caller that everything has been written. */ return to_do == 0 ? EOF : n - to_do; /* Try to maintain alignment: write a whole number of blocks. */ block_size = f->_IO_buf_end - f->_IO_buf_base; do_write = to_do - (block_size >= 128 ? to_do % block_size : 0); if (do_write) { count = new_do_write (f, s, do_write); to_do -= count; if (count < do_write) return n - to_do; } /* Now write out the remainder. Normally, this will fit in the buffer, but it's somewhat messier for line-buffered files, so we let _IO_default_xsputn handle the general case. */ if (to_do) to_do -= _IO_default_xsputn (f, s+do_write, to_do); } return n - to_do; } libc_hidden_ver (_IO_new_file_xsputn, _IO_file_xsputn) ``` glibc tested: commit 5c23c82195fc9e95ae34180250f64438f1e6fb0b (HEAD -> makepkg, origin/master, origin/HEAD) Date: Fri May 24 22:14:04 2019 +0200 nss_dns: Check for proper A/AAAA address alignment I'm on ArchLinux. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45583-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 05:20:51 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 3049 invoked by alias); 27 May 2019 05:20:51 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 3011 invoked by uid 48); 27 May 2019 05:20:47 -0000 From: "gentoo-bugzilla at jdrake dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/24595] [2.28 Regression]: Deadlock in atfork handler which calls dlclose Date: Mon, 27 May 2019 05:20: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: 2.28 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: gentoo-bugzilla at jdrake 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00213.txt.bz2 Content-length: 1129 https://sourceware.org/bugzilla/show_bug.cgi?id=24595 --- Comment #7 from Jeremy Drake --- (In reply to Adhemerval Zanella from comment #2) > We need to make the atfork handling to use a recursive mutex and make the > data structure to handle reentracy. Unfortunately, I think the current one > (dynarray) is not the best suitable one due on reentracy the iterator is > usually an index (which might render invalid in an atfork handler removal). > A simple double-linked list should handle it. > > Could you try the attached patch to see if it fixes the issue you are > seeing? I would like just to confirm before sending upstream to review. I finally got a chance to test this in the original situation where I saw the hang, and it seems to do the trick. Even if opensc-0.19.0 has removed a background thread, which causes the hang to no longer trigger due to the 669ff911e2571f74a2668493e326ac9a505776bd commit, your approach seems safer in the case when the list changes while being iterated. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45584-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 05:38:42 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 5774 invoked by alias); 27 May 2019 05:38:42 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 5730 invoked by uid 48); 27 May 2019 05:38:38 -0000 From: "agner at agner dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] New: powl function inaccurate for x86/x86_64 Date: Mon, 27 May 2019 05:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: agner at agner dot org 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 target_milestone attachments.created Message-ID: 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-05/txt/msg00214.txt.bz2 Content-length: 1443 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 Bug ID: 24622 Summary: powl function inaccurate for x86/x86_64 Product: glibc Version: 2.27 Status: UNCONFIRMED Severity: normal Priority: P2 Component: math Assignee: unassigned at sourceware dot org Reporter: agner at agner dot org Target Milestone: --- Created attachment 11804 --> https://sourceware.org/bugzilla/attachment.cgi?id=11804&action=edit Test case for powl accuracy The powl function is less accurate than pow, and in some situations quite inaccurate (both Gcc and Clang). The problem is discussed in bug https://sourceware.org/bugzilla/show_bug.cgi?id=13881 and https://sourceware.org/bugzilla/show_bug.cgi?id=706 , but I was told to file a new bug report. I am attaching a simple test code. More test case: powl(9.4401197044207130E-01,9.0396338480980503E+03) relative error 7.9E-13 powl(9.6205229632635447E-01,9.0396338480980503E+03) relative error 5.1E-13 powl(1.0567906354279399E+00,9.0396338480980503E+03) relative error 5.7E-13 powl(9.5952957579581444E-01,-1.6994966845030955E+04) relative error 1.8E-12 powl(9.4249308583367331E-01,5.1811882606772378E+03) relative error 6.4E-13 powl(1.0537202715568794E+00,5.1811882606772378E+03) relative error 4.2E-13 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45585-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 05:39:37 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 6647 invoked by alias); 27 May 2019 05:39:36 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 6629 invoked by uid 48); 27 May 2019 05:39:33 -0000 From: "agner at agner dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Mon, 27 May 2019 05:39:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: agner at agner dot org 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00215.txt.bz2 Content-length: 1280 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 agner at agner dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |agner at agner dot org --- Comment #1 from agner at agner dot org --- The powl function is less accurate than pow, and in some situations quite inaccurate (both Gcc and Clang). The problem is discussed in bug https://sourceware.org/bugzilla/show_bug.cgi?id=13881 and https://sourceware.org/bugzilla/show_bug.cgi?id=706 , but I was told to file a new bug report. I have attached a simple test code. More test case: powl(9.4401197044207130E-01,9.0396338480980503E+03) relative error 7.9E-13 powl(9.6205229632635447E-01,9.0396338480980503E+03) relative error 5.1E-13 powl(1.0567906354279399E+00,9.0396338480980503E+03) relative error 5.7E-13 powl(9.5952957579581444E-01,-1.6994966845030955E+04) relative error 1.8E-12 powl(9.4249308583367331E-01,5.1811882606772378E+03) relative error 6.4E-13 powl(1.0537202715568794E+00,5.1811882606772378E+03) relative error 4.2E-13 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45586-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 09:09:01 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 10024 invoked by alias); 27 May 2019 09:09:01 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 9989 invoked by uid 48); 27 May 2019 09:08:58 -0000 From: "schwab@linux-m68k.org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Mon, 27 May 2019 09:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00216.txt.bz2 Content-length: 231 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 --- Comment #2 from Andreas Schwab --- How did you compute the error? -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45587-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 11:45:07 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 123551 invoked by alias); 27 May 2019 11:45:05 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 121222 invoked by uid 48); 27 May 2019 11:45:01 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug nptl/24595] [2.28 Regression]: Deadlock in atfork handler which calls dlclose Date: Mon, 27 May 2019 11:45: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: 2.28 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00217.txt.bz2 Content-length: 1405 https://sourceware.org/bugzilla/show_bug.cgi?id=24595 --- Comment #8 from Adhemerval Zanella --- (In reply to Jeremy Drake from comment #7) > (In reply to Adhemerval Zanella from comment #2) > > We need to make the atfork handling to use a recursive mutex and make the > > data structure to handle reentracy. Unfortunately, I think the current one > > (dynarray) is not the best suitable one due on reentracy the iterator is > > usually an index (which might render invalid in an atfork handler removal). > > A simple double-linked list should handle it. > > > > Could you try the attached patch to see if it fixes the issue you are > > seeing? I would like just to confirm before sending upstream to review. > > I finally got a chance to test this in the original situation where I saw > the hang, and it seems to do the trick. Even if opensc-0.19.0 has removed a > background thread, which causes the hang to no longer trigger due to the > 669ff911e2571f74a2668493e326ac9a505776bd commit, your approach seems safer > in the case when the list changes while being iterated. Thanks for confirming this fix at least improve the situation. Florian Weimer has raised some question about the validity of the fix in some cases, so we are still discussion upstream. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45588-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 12:52:28 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 102916 invoked by alias); 27 May 2019 12:52:28 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 98882 invoked by uid 48); 27 May 2019 12:52:24 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Mon, 27 May 2019 12:52:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org 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 attachments.created Message-ID: In-Reply-To: References: 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-05/txt/msg00218.txt.bz2 Content-length: 759 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 Adhemerval Zanella changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adhemerval.zanella at linaro dot o | |rg --- Comment #3 from Adhemerval Zanella --- Created attachment 11806 --> https://sourceware.org/bugzilla/attachment.cgi?id=11806&action=edit Testcase to show ULP difference Build with gcc -Wall -D_GNU_SOURCE test-bz24622.c -lmpfr -lm -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45589-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 12:55:38 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 109331 invoked by alias); 27 May 2019 12:55:38 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 109304 invoked by uid 48); 27 May 2019 12:55:34 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Mon, 27 May 2019 12:55:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00219.txt.bz2 Content-length: 1033 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 --- Comment #4 from Adhemerval Zanella --- (In reply to Andreas Schwab from comment #2) > How did you compute the error? It is using a naive and wrong approach: double a = 2.8016; long double exact = a; for (int i=0; i<9; i++) exact *= exact; Not sure exactly what he is doing or expecting in attachment 11804. I added attachment 11806 with a more complex case: it computes the result using mpfr with 2048 bits and compares against the libm. For ulp and print I just used the glibc libm test infrastructure as base: $ gcc -Wall -D_GNU_SOURCE test-bz24622.c -lmpfr -lm -fno-builtin $ ./a.out Result: is: 1.18015191259911930651e+229 0xf.9164a0cd5896ad70p+757 should be: 1.18015191259911930651e+229 0xf.9164a0cd5896ad70p+757 difference: 0.00000000000000000000e+00 0x0.0000000000000000p+0 ulp : 0.0000 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45590-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 13:02:23 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 114537 invoked by alias); 27 May 2019 13:02:22 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 114502 invoked by uid 48); 27 May 2019 13:02:19 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Mon, 27 May 2019 13:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org 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: attachments.created Message-ID: In-Reply-To: References: 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-05/txt/msg00220.txt.bz2 Content-length: 433 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 --- Comment #5 from Adhemerval Zanella --- Created attachment 11807 --> https://sourceware.org/bugzilla/attachment.cgi?id=11807&action=edit Testcase to show ULP difference gcc -Wall -D_GNU_SOURCE test-bz24622.c -lmpfr -lm -fno-builtin && ./a.out -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45591-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 13:03:45 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 119162 invoked by alias); 27 May 2019 13:03:45 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 119085 invoked by uid 48); 27 May 2019 13:03:41 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Mon, 27 May 2019 13:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00221.txt.bz2 Content-length: 1918 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 --- Comment #6 from Adhemerval Zanella --- And now same test with all other inputs referenced in attachment 11804: $ gcc -Wall -D_GNU_SOURCE test-bz24622.c -lmpfr -lm -fno-builtin && ./a.out Result: is: 6.39402464772996476487e-227 0xc.1e231da8d48a7b00p-755 should be: 6.39402464772996476487e-227 0xc.1e231da8d48a7b00p-755 difference: 0.00000000000000000000e+00 0x0.0000000000000000p+0 ulp : 0.0000 Result: is: 1.32502479835396768714e-152 0xb.1a822bbb696f9ac0p-508 should be: 1.32502479835396768725e-152 0xb.1a822bbb696f9ad0p-508 difference: 1.03505270065976189610e-171 0x8.0000000000000000p-571 ulp : 1.0000 Result: is: 7.10199580719968820392e+216 0xa.4d05377625e46400p+717 should be: 7.10199580719968820392e+216 0xa.4d05377625e46400p+717 difference: 0.00000000000000000000e+00 0x0.0000000000000000p+0 ulp : 0.0000 Result: is: 8.26953694308422555797e+304 0xf.12d4386386b9f530p+1009 should be: 8.26953694308422555797e+304 0xf.12d4386386b9f530p+1009 difference: 0.00000000000000000000e+00 0x0.0000000000000000p+0 ulp : 0.0000 Result: is: 5.37491158622426678496e-134 0x9.c448b9b2ee3b0060p-446 should be: 5.37491158622426678496e-134 0x9.c448b9b2ee3b0060p-446 difference: 0.00000000000000000000e+00 0x0.0000000000000000p+0 ulp : 0.0000 Result: is: 5.54931739964968432968e+117 0x8.cd6a486b778737a0p+388 should be: 5.54931739964968432968e+117 0x8.cd6a486b778737a0p+388 difference: 0.00000000000000000000e+00 0x0.0000000000000000p+0 ulp : 0.0000 So the only one which is not exact is powl (9.6205229632635447E-01L, 9.0396338480980503E+03L) with an 1 ULP of error. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45592-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 14:42:21 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 75844 invoked by alias); 27 May 2019 14:42:21 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 75820 invoked by uid 48); 27 May 2019 14:42:17 -0000 From: "tomi.kyostila at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/14717] Allow choice of clock source for calls to sem_timedwait() and pthread_mutex_timedwait(). Date: Mon, 27 May 2019 14:42: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: enhancement X-Bugzilla-Who: tomi.kyostila at gmail dot com X-Bugzilla-Status: WAITING 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: In-Reply-To: References: 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-05/txt/msg00222.txt.bz2 Content-length: 418 https://sourceware.org/bugzilla/show_bug.cgi?id=14717 Tomi Kyöstilä changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomi.kyostila at gmail dot com -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45593-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 14:47:36 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 82682 invoked by alias); 27 May 2019 14:47:35 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 82642 invoked by uid 48); 27 May 2019 14:47:32 -0000 From: "tomi.kyostila at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug nptl/15555] pthread_condattr_setclock should accept CLOCK_MONOTONIC_COARSE, CLOCK_MONOTONIC_RAW Date: Mon, 27 May 2019 14:47: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: enhancement X-Bugzilla-Who: tomi.kyostila at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: 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-05/txt/msg00223.txt.bz2 Content-length: 418 https://sourceware.org/bugzilla/show_bug.cgi?id=15555 Tomi Kyöstilä changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomi.kyostila at gmail dot com -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45594-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon May 27 20:44:26 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 128318 invoked by alias); 27 May 2019 20:44:26 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 128236 invoked by uid 48); 27 May 2019 20:44:22 -0000 From: "adhemerval.zanella at linaro dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Mon, 27 May 2019 20:44:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00224.txt.bz2 Content-length: 403 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 --- Comment #7 from Adhemerval Zanella --- The results align with the maximum expected ULPs of 9 for x86_64 long double (math/libm-test-support.c:237), so imho there is no issue here (at least not with the input referenced). -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45595-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 00:36:40 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 16786 invoked by alias); 28 May 2019 00:36:40 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 16731 invoked by uid 48); 28 May 2019 00:36:37 -0000 From: "carlos at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug locale/18830] iconv -c -f ascii with >buffer size worth of input before invalid input drops valid char Date: Tue, 28 May 2019 00:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: locale 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: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: 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-05/txt/msg00225.txt.bz2 Content-length: 547 https://sourceware.org/bugzilla/show_bug.cgi?id=18830 Carlos O'Donell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos at redhat dot com --- Comment #1 from Carlos O'Donell --- Patch under review: https://www.sourceware.org/ml/libc-alpha/2019-05/msg00594.html -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45596-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 07:20:51 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 49166 invoked by alias); 28 May 2019 07:20:50 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 49110 invoked by uid 48); 28 May 2019 07:20:46 -0000 From: "agner at agner dot org" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Tue, 28 May 2019 07:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: agner at agner dot org 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00226.txt.bz2 Content-length: 2141 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 --- Comment #8 from agner at agner dot org --- Thank you very much for making a test program for this. It appears that the error occurs only when running Ubuntu as a subsystem under Windows (WSL). It claims to be a genuine Ubuntu, and it appears to be - except for the powl bug. My configuration: uname -a Linux DESKTOP-08PNUTF 4.4.0-17763-Microsoft #379-Microsoft Wed Mar 06 19:16:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux gcc --version gcc (Ubuntu 7.4.0-1ubuntu1~18.04) 7.4.0 libc version 2.27 Result of Adhemerval's test program: ------------------------------------ a = 2.8016; b = 512; is: 1.18015191259917123727e+229 0xf.9164a0cd59578000p+757 should be: 1.18015191259911930651e+229 0xf.9164a0cd5896ad70p+757 difference: 5.19307574397350868049e+215 0xc.0d29000000000000p+713 ulp : 789801.0000 a = 9.5952957579581444E-01; b = -1.6994966845030955E+04; Result: is: 8.26953694309959887315e+304 0xf.12d43863a5898000p+1009 should be: 8.26953694308439751375e+304 0xf.12d4386387122ec0p+1009 difference: 1.52013593940156453233e+293 0xf.3ba8a00000000000p+970 ulp : 31946004.0000 I tried to test powl in various other sytems: Clean Ubuntu installation: powl is accurate Mingw64: powl is accurate Cygwin64: powl is accurate Ubuntu in Windows Subsystem for Linux: powl is inaccurate! My apologies for not reporting the complete system configuration. I believed the claim that it was a genuine Ubuntu, and in all other respects it appears to be. Is there a fork of glibc somewhere, and who is responsible for it? Or is it a configuration error? The little test program i attached calculates a special case of powl(x,y) where y is a power of 2. This makes the exact calculation very simple. In the other test cases I reported, I calculated the reference value by splitting y into an integer part and a fraction. I get basically the same results as your test program, but of course a mpfr is better. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45597-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 07:29:37 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 69570 invoked by alias); 28 May 2019 07:29:37 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 69532 invoked by uid 48); 28 May 2019 07:29:33 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Tue, 28 May 2019 07:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: fweimer at redhat 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: security- X-Bugzilla-Changed-Fields: bug_status cc see_also resolution Message-ID: In-Reply-To: References: 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-05/txt/msg00227.txt.bz2 Content-length: 1230 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |fweimer at redhat dot com See Also| |https://github.com/Microsof | |t/WSL/issues/830 Resolution|--- |INVALID --- Comment #9 from Florian Weimer --- (In reply to agner@agner.org from comment #8) > Thank you very much for making a test program for this. > > It appears that the error occurs only when running Ubuntu as a subsystem > under Windows (WSL). long double is completely broken under WSL. Microsoft refuses to fix this: https://github.com/Microsoft/WSL/issues/830 It is unclear why this bug even exists. If there is a deeper Windows kernel issue involved, we should not try to paper over it in glibc because it could expose that other bug. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45598-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 13:42:28 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 54799 invoked by alias); 28 May 2019 13:42:27 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 54719 invoked by uid 48); 28 May 2019 13:42:24 -0000 From: "dflogeras2 at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/23960] [2.28 Regression]: New getdents{64} implementation breaks qemu-user Date: Tue, 28 May 2019 13:42: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.28 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dflogeras2 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: security- X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: 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-05/txt/msg00228.txt.bz2 Content-length: 591 https://sourceware.org/bugzilla/show_bug.cgi?id=23960 --- Comment #48 from dflo --- Created attachment 11808 --> https://sourceware.org/bugzilla/attachment.cgi?id=11808&action=edit Patch to bypass the return EOVERFLOW condition Here's a patch I tried as a proof of concept. I #if'd out the check for overflow in getdents.c, and installed glibc-2.29 in a gentoo chroot. This worked around any issues with all of the packages that I noticed broken prior to the change. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45599-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 16:48:48 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 41688 invoked by alias); 28 May 2019 16:48:48 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 41514 invoked by uid 55); 28 May 2019 16:48:24 -0000 From: "joseph at codesourcery dot com" To: glibc-bugs@sourceware.org Subject: [Bug math/24622] powl function inaccurate for x86/x86_64 Date: Tue, 28 May 2019 16:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: 2.27 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery 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: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-05/txt/msg00229.txt.bz2 Content-length: 1682 https://sourceware.org/bugzilla/show_bug.cgi?id=24622 --- Comment #10 from joseph at codesourcery dot com --- On Tue, 28 May 2019, agner at agner dot org wrote: > The little test program i attached calculates a special case of powl(x,y) where > y is a power of 2. This makes the exact calculation very simple. In the other Repeated squaring is *not* an exact calculation, as errors can accumulate as soon as intermediate results are inexact. It's a technique for integer exponents that I removed for all but very small exponents in commit 1bead169c32a3a688de863709b863207b7aafddd to fix bug 13881, precisely because it's an excessively inaccurate technique. The simplest way to cross-check results against MPFR, if you're set up to regenerate glibc libm test results, is to add the test inputs to math/auto-libm-test-in and then use gen-auto-libm-tests to regenerate the expectations, and run the glibc libm tests (which shows that none of the inputs in this bug have errors larger than expected). I also advise giving libm test inputs as hex float values, to avoid any ambiguity about whether you mean the exact decimal value, or that value rounded to double, or that value rounded to long double. I don't know if the move of WSL to using a real Linux kernel will address the WSL issue described here, but one might hope it would improve glibc test results under WSL in general (see the per-release wiki pages for the results of such test runs). -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45600-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 18:45:40 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 7725 invoked by alias); 28 May 2019 18:45:24 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 7393 invoked by uid 48); 28 May 2019 18:45:04 -0000 From: "tuliom at ascii dot art.br" To: glibc-bugs@sourceware.org Subject: [Bug math/24209] [powerpc] Enable exp/expf in libmvec vector math library on POWER VSX Date: Tue, 28 May 2019 18:45:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tuliom at ascii dot art.br 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00230.txt.bz2 Content-length: 321 https://sourceware.org/bugzilla/show_bug.cgi?id=24209 --- Comment #1 from Tulio Magno Quites Machado Filho --- The single precision implementation has just been merged. The double precision is under review. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45601-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 20:17:13 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 9424 invoked by alias); 28 May 2019 20:17:13 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 9380 invoked by uid 55); 28 May 2019 20:17:10 -0000 From: "cvs-commit at gcc dot gnu.org" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24369] Orthographic mistakes in 'mon' and 'abmon' sections in tt_RU (Tatar) locale Date: Tue, 28 May 2019 20:17: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00231.txt.bz2 Content-length: 1044 https://sourceware.org/bugzilla/show_bug.cgi?id=24369 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Rafal Luzynski : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=182a3746b8cc28784718c8ea27346e97d1423945 commit 182a3746b8cc28784718c8ea27346e97d1423945 Author: mansayk <6688000@gmail.com> Date: Sat Mar 16 11:33:30 2019 +0300 tt_RU: Fix orthographic mistakes in mon and abmon sections [BZ #24369] This commit fixes some errors and converts all month names to lowercase. The content is synchronized with CLDR-35.1 now but trailing dots are removed from abmon values in order to maintain consistency with the previous values and with many other locales which do the same. [BZ #24369] * localedata/locales/tt_RU (mon): Update from CLDR-35.1, fix errors. (abmon): Likewise, but remove the trailing dots. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45602-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 20:17:21 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 10047 invoked by alias); 28 May 2019 20:17:20 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 9902 invoked by uid 55); 28 May 2019 20:17:17 -0000 From: "cvs-commit at gcc dot gnu.org" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24370] Add lang_name for tt_RU locale Date: Tue, 28 May 2019 20:17: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: cvs-commit at gcc dot gnu.org 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00232.txt.bz2 Content-length: 708 https://sourceware.org/bugzilla/show_bug.cgi?id=24370 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Rafal Luzynski : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=157cda1ff0b75937521b155f7a4d5b4ec865b750 commit 157cda1ff0b75937521b155f7a4d5b4ec865b750 Author: mansayk <6688000@gmail.com> Date: Sat Mar 16 11:46:39 2019 +0300 tt_RU: Add lang_name [BZ #24370] This commit adds a lang_name according to CLDR-35.1. [BZ #24370] * localedata/locales/tt_RU (lang_name): Add from CLDR-35.1. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45603-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 20:36:31 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 51200 invoked by alias); 28 May 2019 20:36:31 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 48851 invoked by uid 48); 28 May 2019 20:36:27 -0000 From: "digitalfreak at lingonborough dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24369] Orthographic mistakes in 'mon' and 'abmon' sections in tt_RU (Tatar) locale Date: Tue, 28 May 2019 20:36: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: digitalfreak at lingonborough dot com 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: bug_status cc resolution Message-ID: In-Reply-To: References: 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-05/txt/msg00233.txt.bz2 Content-length: 945 https://sourceware.org/bugzilla/show_bug.cgi?id=24369 Rafal Luzynski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |digitalfreak@lingonborough. | |com Resolution|--- |FIXED --- Comment #3 from Rafal Luzynski --- Thank you for your bug report and the patch, and I'm sorry for the delay. During that time, CLDR 35 and 35.1 have been released. I have verified that your updates match the newest version 35.1. Therefore I tweaked your commit message to refer to 35.1, added ChangeLog, and pushed. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45604-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 20:39:22 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 65712 invoked by alias); 28 May 2019 20:39:22 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 61848 invoked by uid 48); 28 May 2019 20:39:19 -0000 From: "digitalfreak at lingonborough dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24370] Add lang_name for tt_RU locale Date: Tue, 28 May 2019 20:39: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: digitalfreak at lingonborough dot com 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: bug_status cc resolution Message-ID: In-Reply-To: References: 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-05/txt/msg00234.txt.bz2 Content-length: 975 https://sourceware.org/bugzilla/show_bug.cgi?id=24370 Rafal Luzynski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |digitalfreak@lingonborough. | |com Resolution|--- |FIXED --- Comment #3 from Rafal Luzynski --- Thank you for the bug report and the patch. Again I am sorry for the delay. Since the versions 35 and 35.1 of CLDR have been released I have edited your commit message, added ChangeLog, and pushed. Also I did a little alignment tweak in your patch so you may notice a merge conflict in your local git repo. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45605-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 21:45:48 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 114768 invoked by alias); 28 May 2019 21:45:47 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 108287 invoked by uid 48); 28 May 2019 21:45:36 -0000 From: "digitalfreak at lingonborough dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24369] Orthographic mistakes in 'mon' and 'abmon' sections in tt_RU (Tatar) locale Date: Tue, 28 May 2019 21:45: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: digitalfreak at lingonborough dot com 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: 2.30 X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: target_milestone Message-ID: In-Reply-To: References: 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-05/txt/msg00235.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=24369 Rafal Luzynski changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.30 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45606-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 21:46:14 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 129008 invoked by alias); 28 May 2019 21:46:14 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 127482 invoked by uid 48); 28 May 2019 21:46:11 -0000 From: "digitalfreak at lingonborough dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24370] Add lang_name for tt_RU locale Date: Tue, 28 May 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: localedata X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: digitalfreak at lingonborough dot com 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: 2.30 X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: target_milestone Message-ID: In-Reply-To: References: 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-05/txt/msg00236.txt.bz2 Content-length: 388 https://sourceware.org/bugzilla/show_bug.cgi?id=24370 Rafal Luzynski changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.30 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45607-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 22:35:53 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 130393 invoked by alias); 28 May 2019 22:35:53 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 130329 invoked by uid 48); 28 May 2019 22:35:49 -0000 From: "digitalfreak at lingonborough dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24614] nl_NL LC_MONETARY doesn't match CLDR 27 Date: Tue, 28 May 2019 22:35: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.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: digitalfreak at lingonborough 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: In-Reply-To: References: 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-05/txt/msg00237.txt.bz2 Content-length: 571 https://sourceware.org/bugzilla/show_bug.cgi?id=24614 --- Comment #7 from Rafal Luzynski --- (In reply to sjon from comment #5) > [...] and I'd suggest keeping that discussion in #23831. You are right. Sorry for the noise. I was thinking about fixing those two bugs with one commit. I have no more questions about this particular issue so if I don't resolve missing questions about bug 23831 then I'll just push a solution for this one. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45608-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue May 28 22:43:22 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 10516 invoked by alias); 28 May 2019 22:43:22 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 10453 invoked by uid 48); 28 May 2019 22:43:19 -0000 From: "digitalfreak at lingonborough dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/23831] nl_NL missing LC_NUMERIC thousands_sep Date: Tue, 28 May 2019 22:43: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: digitalfreak at lingonborough 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: In-Reply-To: References: 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-05/txt/msg00238.txt.bz2 Content-length: 1404 https://sourceware.org/bugzilla/show_bug.cgi?id=23831 Rafal Luzynski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |digitalfreak@lingonborough. | |com --- Comment #2 from Rafal Luzynski --- Patch is not needed unless you want to see your name in the changelog and in the commit log. :-) There was a little discussion in bug 21614 (yes, incorrectly placed) about the correct value of thousands_sep and mon_thousands_sep. In short: * currently thousands_sep is empty and mon_thousands_sep is a narrow no-break space, * in this report it has been said that thousands_sep should be a single dot, * nothing has been said about mon_thousands_sep, is it correct now? It seems to me that some people prefer a space, some prefer a dot. CLDR which is our authoritative source says it should be a dot but it is not clear to me whether the dot should be applied to mon_thousands_sep (monetary format) or thousands_sep (other numeric formats) or maybe both. Is there a context where a space (especially a narrow no-break space) would be preferred? -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45609-listarch-glibc-bugs=sources.redhat.com@sourceware.org Wed May 29 08:07:39 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 104612 invoked by alias); 29 May 2019 08:07:39 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 104554 invoked by uid 48); 29 May 2019 08:07:36 -0000 From: "6688000 at gmail dot com" To: glibc-bugs@sourceware.org Subject: [Bug localedata/24369] Orthographic mistakes in 'mon' and 'abmon' sections in tt_RU (Tatar) locale Date: Wed, 29 May 2019 08:07: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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: 6688000 at gmail dot com 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: 2.30 X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-05/txt/msg00239.txt.bz2 Content-length: 230 https://sourceware.org/bugzilla/show_bug.cgi?id=24369 --- Comment #4 from mansur <6688000 at gmail dot com> --- Hi, Rafal! Great news! Thank you. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45610-listarch-glibc-bugs=sources.redhat.com@sourceware.org Wed May 29 13:58:24 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 80975 invoked by alias); 29 May 2019 13:58:24 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 80934 invoked by uid 48); 29 May 2019 13:58:21 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug ports/13556] Remove ARM old-ABI support Date: Wed, 29 May 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: ports 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: jsm28 at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: 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-05/txt/msg00240.txt.bz2 Content-length: 397 https://sourceware.org/bugzilla/show_bug.cgi?id=13556 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45611-listarch-glibc-bugs=sources.redhat.com@sourceware.org Wed May 29 16:06:19 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 117679 invoked by alias); 29 May 2019 16:06:19 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 117481 invoked by uid 48); 29 May 2019 16:06:16 -0000 From: "yann at droneaud dot fr" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/23462] Static binary with dynamic string tokens crashes. Date: Wed, 29 May 2019 16:06: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: yann at droneaud dot fr 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 Message-ID: In-Reply-To: References: 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-05/txt/msg00241.txt.bz2 Content-length: 392 https://sourceware.org/bugzilla/show_bug.cgi?id=23462 Yann Droneaud changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yann at droneaud dot fr -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45612-listarch-glibc-bugs=sources.redhat.com@sourceware.org Thu May 30 20:19:09 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 30654 invoked by alias); 30 May 2019 20:19:09 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 30612 invoked by uid 48); 30 May 2019 20:19:05 -0000 From: "yann at droneaud dot fr" To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/24561] _dl_addr: linear lookup inefficient, making mtrace() feature very slow Date: Thu, 30 May 2019 20:19: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: yann at droneaud dot fr 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: Message-ID: In-Reply-To: References: 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-05/txt/msg00242.txt.bz2 Content-length: 2009 https://sourceware.org/bugzilla/show_bug.cgi?id=24561 --- Comment #6 from Yann Droneaud --- (In reply to Yann Droneaud from comment #5) > (In reply to Florian Weimer from comment #4) > > Sorry, this came across wrong. If someone else has a patch for this, I'll > > gladly review it. > > OK, I'm investigating. > It's not as easy as I expected. determine_info() has to search through *all* the symbols to find the one the closest to the address being looked up. *all* because: 1) the symbols are not ordered by address 2) the symbols can overlap. Also the number of symbols is possibly unknown as .dynamic section doesn't contains a tag that could provide such information. Thanks, no thanks, ELF specification. we have DT_STRSZ, DT_SYMENT, but no DT_SYMSZ ! In the presence of a DT_GNU_HASH table, every items present in the table is accessed, so there's no need to know the number of symbols. When DT_GNU_HASH is not available *and* a DT_HASH hash is present, the DT_HASH's nchain is the number of symbols. When there neither DT_GNU_HASH nor DT_HASH (is that even possible ?) a dubious assumption is made regarding the placement of the symbol table relative to the string table. I've failed to find a note about it in ELF specification. Anyway, all symbols should be inspected. And that's what determine_info() does, every time. It could be possible to put every symbols in a dedicated data structure (per DSO, in link_map) on first call do dladdr(). At first glance, interval tree seems to be the solution for faster lookup. But I'm not going to invest time adding a dedicated tree implementation without any prior feedback. Sorting the symbols by start address could be a first step, allowing the search to end as soon as next symbol is after the address being looked up. Note that binary search would not be possible in this partial optimisation. Any idea ? -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45613-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 09:22:04 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 72886 invoked by alias); 3 Jun 2019 09:22:03 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 72828 invoked by uid 48); 3 Jun 2019 09:21:59 -0000 From: "osmith at sysmocom dot de" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] New: mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Mon, 03 Jun 2019 09:22: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: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: osmith at sysmocom 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 target_milestone Message-ID: 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-06/txt/msg00000.txt.bz2 Content-length: 1351 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 Bug ID: 24630 Summary: mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Product: glibc Version: 2.29 Status: UNCONFIRMED Severity: normal Priority: P2 Component: time Assignee: unassigned at sourceware dot org Reporter: osmith at sysmocom dot de Target Milestone: --- mktime fails in an osmo-hlr test case with glibc 2.29 on ubuntu 19.04 with "Value too large for defined data type" [1]. The same test works fine on other linux distributions with earlier glibc versions. There is another downstream bug report with these symptoms for glibc 2.28 in the fedora bug tracker, and it has a reproducer in the description [2]. I was able to reproduce the problem with that test program, on ubuntu 19.04 with glibc 2.29. Just like it says in the fedora tracker, the bug happens with the timezone set to UTC, but not if it is set to CET. The same workaround helps with the osmo-hlr test case. So it seems that this is a regression in glibc. [1]: https://osmocom.org/issues/4026 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1653340#c0 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45614-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 09:46:45 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 19935 invoked by alias); 3 Jun 2019 09:46:45 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 17783 invoked by uid 48); 3 Jun 2019 09:46:42 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Mon, 03 Jun 2019 09:46: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: 2.29 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 see_also flagtypes.name Message-ID: In-Reply-To: References: 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-06/txt/msg00001.txt.bz2 Content-length: 609 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com See Also| |https://bugzilla.redhat.com | |/show_bug.cgi?id=1653340 Flags| |security- -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45615-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 09:50:08 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 77487 invoked by alias); 3 Jun 2019 09:50:07 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 73528 invoked by uid 48); 3 Jun 2019 09:50:04 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Mon, 03 Jun 2019 09:50: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: 2.29 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: Message-ID: In-Reply-To: References: 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-06/txt/msg00002.txt.bz2 Content-length: 419 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 --- Comment #1 from Florian Weimer --- Would you please provide a minimal reproducer (C source code with the required setenv/tzset/mktime calls)? Thanks. If you use TZ=CEST, then it's actually an alias for UTC. The Fedora reproducer is invalid. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45616-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 10:03:04 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 69524 invoked by alias); 3 Jun 2019 10:03:04 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 63327 invoked by uid 48); 3 Jun 2019 10:03:00 -0000 From: "osmith at sysmocom dot de" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Mon, 03 Jun 2019 10:03: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: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: osmith at sysmocom 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: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-06/txt/msg00003.txt.bz2 Content-length: 379 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 --- Comment #2 from Oliver Smith --- I think the fedora reproducer is valid. I did not use TZ=CEST, but TZ=CET. As written above: > the bug happens with the timezone set to UTC, but not if it is set to CET. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45617-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 10:16:25 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 5606 invoked by alias); 3 Jun 2019 10:16:25 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 5562 invoked by uid 48); 3 Jun 2019 10:16:22 -0000 From: "schwab@linux-m68k.org" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Mon, 03 Jun 2019 10:16: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: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org 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: Message-ID: In-Reply-To: References: 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-06/txt/msg00004.txt.bz2 Content-length: 241 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 --- Comment #3 from Andreas Schwab --- But TZ=CET works, so where is the bug? -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45618-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 10:22:05 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 10745 invoked by alias); 3 Jun 2019 10:22:05 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 10698 invoked by uid 48); 3 Jun 2019 10:22:02 -0000 From: "dinghao at zcool dot com.cn" To: glibc-bugs@sourceware.org Subject: [Bug libc/22375] malloc returns pointer from tcache_get when should return NULL (CVE-2017-17426) Date: Mon, 03 Jun 2019 10: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: 2.26 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dinghao at zcool dot com.cn X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: arjun.is at lostca dot se X-Bugzilla-Target-Milestone: 2.27 X-Bugzilla-Flags: security+ X-Bugzilla-Changed-Fields: cc attachments.created Message-ID: In-Reply-To: References: 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-06/txt/msg00005.txt.bz2 Content-length: 568 https://sourceware.org/bugzilla/show_bug.cgi?id=22375 dinghao changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dinghao at zcool dot com.cn --- Comment #11 from dinghao --- Created attachment 11811 --> https://sourceware.org/bugzilla/attachment.cgi?id=11811&action=edit 1111 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45619-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 11:19:13 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 123051 invoked by alias); 3 Jun 2019 11:19:13 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 123022 invoked by uid 48); 3 Jun 2019 11:19:10 -0000 From: "osmith at sysmocom dot de" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Mon, 03 Jun 2019 11:19: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: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: osmith at sysmocom 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: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-06/txt/msg00006.txt.bz2 Content-length: 555 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 --- Comment #4 from Oliver Smith --- The bug is, that it does not work with TZ=UTC. Ubuntu 19.04, glibc 2.29: $ TZ=CET ./reproducer Mon Mar 12 00:01:00 2012 $ TZ=UTC ./reproducer Error: unable to make time using mktime: Value too large for defined data type Debian 9, glibc 2.24: $ TZ=CET ./reproducer Mon Mar 12 00:01:00 2012 $ TZ=UTC ./reproducer Mon Mar 12 01:01:00 2012 -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45620-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 11:27:44 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 35125 invoked by alias); 3 Jun 2019 11:27:43 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 35052 invoked by uid 48); 3 Jun 2019 11:27:39 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/22375] malloc returns pointer from tcache_get when should return NULL (CVE-2017-17426) Date: Mon, 03 Jun 2019 11: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.26 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: arjun.is at lostca dot se X-Bugzilla-Target-Milestone: 2.27 X-Bugzilla-Flags: security+ X-Bugzilla-Changed-Fields: attachments.isobsolete Message-ID: In-Reply-To: References: 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-06/txt/msg00007.txt.bz2 Content-length: 423 https://sourceware.org/bugzilla/show_bug.cgi?id=22375 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #11811|0 |1 is obsolete| | -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45621-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 12:26:29 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 28155 invoked by alias); 3 Jun 2019 12:26:29 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 28114 invoked by uid 48); 3 Jun 2019 12:26:26 -0000 From: "schwab@linux-m68k.org" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Mon, 03 Jun 2019 12:26: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: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: schwab@linux-m68k.org 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: Message-ID: In-Reply-To: References: 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-06/txt/msg00008.txt.bz2 Content-length: 239 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 --- Comment #5 from Andreas Schwab --- But that is not a valid use of mktime. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45622-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 13:03:45 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 32877 invoked by alias); 3 Jun 2019 13:03:45 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 32841 invoked by uid 48); 3 Jun 2019 13:03:41 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug stdio/24632] New: Old binaries which use freopen with default stdio handles crash Date: Mon, 03 Jun 2019 13:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: stdio X-Bugzilla-Version: 2.30 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 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 target_milestone flagtypes.name Message-ID: 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-06/txt/msg00009.txt.bz2 Content-length: 1309 https://sourceware.org/bugzilla/show_bug.cgi?id=24632 Bug ID: 24632 Summary: Old binaries which use freopen with default stdio handles crash Product: glibc Version: 2.30 Status: NEW Severity: minor Priority: P3 Component: stdio Assignee: unassigned at sourceware dot org Reporter: fweimer at redhat dot com Target Milestone: --- Flags: security- Old i386 binaries which use a copy relocation for the backing symbol of stdin/stdout/stderr (_IO_stdin_, _IO_stdout_, _IO_stderr_) and try to reopen that handle crash. With current glibc, this results in “Fatal error: glibc detected an invalid stdio handle”. With older versions, the result is a segmentation fault when the handle is used to call a virtual function (I've seen a NULL pointer dereference). gcc 2.7.2.3-7 from Debian reproduces this when compiling a file which triggers a preprocessor error (e.g., “#include ”). Binaries with wrapper scripts are also available at . -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45623-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Jun 03 13:12:39 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 62104 invoked by alias); 3 Jun 2019 13:12:38 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 62076 invoked by uid 48); 3 Jun 2019 13:12:34 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug stdio/24632] Old binaries which use freopen with default stdio handles crash Date: Mon, 03 Jun 2019 13:12: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: 2.30 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 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: In-Reply-To: References: 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-06/txt/msg00010.txt.bz2 Content-length: 832 https://sourceware.org/bugzilla/show_bug.cgi?id=24632 Florian Weimer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |fweimer at redhat dot com --- Comment #1 from Florian Weimer --- The reason is that freopen does not write the vtable pointer to the right offset, so the vtable offset is clobbered, and subsequent reads fail to produce the right pointer. This is not a recent regression at all. I see it with our version derived from glibc 2.5, too. (That is 2.5, not 2.25.) -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45624-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Jun 04 09:18:29 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 91255 invoked by alias); 4 Jun 2019 09:18:29 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 91219 invoked by uid 48); 4 Jun 2019 09:18:26 -0000 From: "osmith at sysmocom dot de" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Tue, 04 Jun 2019 09:18: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: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: osmith at sysmocom 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: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-06/txt/msg00011.txt.bz2 Content-length: 468 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 --- Comment #6 from Oliver Smith --- I could not find a source that says using mktime with UTC is not allowed. Would you mind explaining why that is the case? Furthermore, mktime seems to be the recommended way to convert "struct tm" to time_t. Do you have a recommendation of what to use instead? -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45625-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Jun 04 09:24:56 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 104297 invoked by alias); 4 Jun 2019 09:24:55 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 104267 invoked by uid 48); 4 Jun 2019 09:24:53 -0000 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Tue, 04 Jun 2019 09:24: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: 2.29 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: Message-ID: In-Reply-To: References: 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-06/txt/msg00012.txt.bz2 Content-length: 481 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 --- Comment #7 from Florian Weimer --- (In reply to Oliver Smith from comment #6) > I could not find a source that says using mktime with UTC is not allowed. > Would you mind explaining why that is the case? tm_isdst == 1 for UTC is invalid input for mktime. It is unclear what you are trying to accomplish. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45626-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Jun 04 10:13:46 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 33220 invoked by alias); 4 Jun 2019 10:13:46 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 33183 invoked by uid 48); 4 Jun 2019 10:13:43 -0000 From: "osmith at sysmocom dot de" To: glibc-bugs@sourceware.org Subject: [Bug time/24630] mktime fails with certain timezones since glibc 2.28: "Value too large for defined data type" Date: Tue, 04 Jun 2019 10:13: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: 2.29 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: osmith at sysmocom dot de 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: security- X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: 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-06/txt/msg00013.txt.bz2 Content-length: 919 https://sourceware.org/bugzilla/show_bug.cgi?id=24630 Oliver Smith changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #8 from Oliver Smith --- I realize now that you also had pointed that out in the other bug report, sorry for not reading it carefully enough. Now I see what is going on, and the problem was in our code. We were converting a date string with strptime() to "struct tm", and then with mktime() to time_t. But our "struct tm" was not initialized, and strptime() does not set tm_isdst, so tm_isdst had a random value. Closing. Thank you! -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45627-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Jun 04 12:05:14 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 79271 invoked by alias); 4 Jun 2019 12:05:14 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 75126 invoked by uid 55); 4 Jun 2019 12:05:11 -0000 From: "cvs-commit at gcc dot gnu.org" To: glibc-bugs@sourceware.org Subject: [Bug locale/18830] iconv -c -f ascii with >buffer size worth of input before invalid input drops valid char Date: Tue, 04 Jun 2019 12:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: locale 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: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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-06/txt/msg00014.txt.bz2 Content-length: 603 https://sourceware.org/bugzilla/show_bug.cgi?id=18830 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Andreas Schwab : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=4802be92c891903caaf8cae47f685da6f26d4b9a commit 4802be92c891903caaf8cae47f685da6f26d4b9a Author: Andreas Schwab Date: Mon Aug 17 14:05:01 2015 +0200 Fix iconv buffer handling with IGNORE error handler (bug #18830) -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45628-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Jun 04 12:13:06 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 109099 invoked by alias); 4 Jun 2019 12:13:06 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 108831 invoked by uid 48); 4 Jun 2019 12:13:03 -0000 From: "schwab@linux-m68k.org" To: glibc-bugs@sourceware.org Subject: [Bug locale/18830] iconv -c -f ascii with >buffer size worth of input before invalid input drops valid char Date: Tue, 04 Jun 2019 12:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: locale 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: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: 2.30 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone Message-ID: In-Reply-To: References: 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-06/txt/msg00015.txt.bz2 Content-length: 556 https://sourceware.org/bugzilla/show_bug.cgi?id=18830 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |2.30 --- Comment #3 from Andreas Schwab --- Fixed. -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45630-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Jun 04 20:03:20 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 128061 invoked by alias); 4 Jun 2019 20:03:20 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 128003 invoked by uid 48); 4 Jun 2019 20:03:16 -0000 From: "tuliom at ascii dot art.br" To: glibc-bugs@sourceware.org Subject: [Bug math/20123] [powerpc] Enable libmvec vector math library on POWER VSX Date: Tue, 04 Jun 2019 20:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: dep_changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tuliom at ascii dot art.br 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_status resolution Message-ID: In-Reply-To: References: 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-06/txt/msg00017.txt.bz2 Content-length: 583 https://sourceware.org/bugzilla/show_bug.cgi?id=20123 Bug 20123 depends on bug 24209, which changed state. Bug 24209 Summary: [powerpc] Enable exp/expf in libmvec vector math library on POWER VSX https://sourceware.org/bugzilla/show_bug.cgi?id=24209 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45629-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Jun 04 20:03:20 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 128057 invoked by alias); 4 Jun 2019 20:03:19 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 127983 invoked by uid 48); 4 Jun 2019 20:03:16 -0000 From: "tuliom at ascii dot art.br" To: glibc-bugs@sourceware.org Subject: [Bug math/24209] [powerpc] Enable exp/expf in libmvec vector math library on POWER VSX Date: Tue, 04 Jun 2019 20:03:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: tuliom at ascii dot art.br 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: bug_status resolution Message-ID: In-Reply-To: References: 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-06/txt/msg00016.txt.bz2 Content-length: 730 https://sourceware.org/bugzilla/show_bug.cgi?id=24209 Tulio Magno Quites Machado Filho changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Tulio Magno Quites Machado Filho --- The double precision implementation has just been merged to branch tuliom/libmvec: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=98dd9ae7654375f9daf559cbb6c0ffa31fc5142b -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-45631-listarch-glibc-bugs=sources.redhat.com@sourceware.org Tue Jun 04 21:22:58 2019 Return-Path: Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 104406 invoked by alias); 4 Jun 2019 21:22:57 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 104399 invoked by uid 89); 4 Jun 2019 21:22:57 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.5 required=5.0 testsYES_60,GIT_PATCH_2,HTML_MESSAGE,KAM_SHORT,RCVD_IN_DNSWL_NONE,T_END_FUTURE_EMAILS,UNSUBSCRIBE_BODY autolearn=no version=3.3.1 spammy=HX-MSMail-Priority:High, campaigns, utm_content, UD:avast.com X-HELO: n1nlsmtp01.shr.prod.ams1.secureserver.net Received: from n1nlsmtp01.shr.prod.ams1.secureserver.net (HELO n1nlsmtp01.shr.prod.ams1.secureserver.net) (188.121.43.201) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 04 Jun 2019 21:22:56 +0000 Received: from n3plcpnl0099.prod.ams3.secureserver.net ([160.153.153.167]) by : HOSTING RELAY : with ESMTP id YGsShSr9y7E3dYGsShEkL2; Tue, 04 Jun 2019 14:21:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=oceanmicrowebzone.com; sfault; h=Content-Type:MIME-Version:Message-ID: Date:Subject:To:From:Reply-To:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Truh4FEB0b8j7gBmDoYCU+6FA5a3ilwT+8X/+Q8RVxU=; b=mY1eWSoHoPGXfE0LCYM70JfzH3 gkmsF3gUIQDCN5ajYTDotC3WhVz3+Dx0vjIeJEBiF+7g5nQtHbtHkT9i6/x7ucpe3hEp3IYl+vwAK fnb48WHjRDp37HRDzahSenqu3iQqnAQaXXYH6CagBBIlrTsqsW5wBFq0bZMMrQEn+MxHnvJ3R/2y0 2VmkGqCKcDk/B9jTImayrffpIzXQPbeteQxftVbZzJvDzkoWXo+8EtXHLMlo4Ug46RQyoxr9CXvm3 S0rM8ok6YK0UR5vhscdUXTSrV4NMcb365fIrF3vtFwaOsuEDUdve3s1uVwxNVpsGcNDjGiOmCw+Ee DLecBAIw==; Received: from [207.244.100.148] (portP303 helo=WS19) by n3plcpnl0099.prod.ams3.secureserver.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.91) (envelope-from ) id 1hYGsK-002MYA-JV for glibc-bugs@sourceware.org; Tue, 04 Jun 2019 14:21:45 -0700 Reply-To: From: "Jessica Stewart" To: Subject: Alcatel Lucent Potential Business Leads Date: Tue, 04 Jun 2019 21:22:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-SW-Source: 2019-06/txt/msg00018.txt.bz2 Content-length: 453 Hi, I wanted to check if you'd be interested in acquiring Alcatel Lucent Users List for your sales and marketing campaigns? Let me know if you are interested and I will get back to you with the counts and pricing. Regards, Jessica Stewart Sr. Demand Generation Manager To stop receiving future emails, please reply with UNSUBSCRIBE in the Subject Line. --- This email has been checked for viruses by AVG. https://www.avg.com