public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/31509] Invalid read in __wcpncpy_avx2() via wcsxfrm()
Date: Tue, 19 Mar 2024 12:53:32 +0000 [thread overview]
Message-ID: <bug-31509-131-MMb4JLnYUS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31509-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31509
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Sebastian Dröge from comment #0)
> ==139735== Invalid read of size 32
> ==139735== at 0x49DAA2E: __wcpncpy_avx2 (strncpy-avx2.S:85)
> ==139735== by 0x493C560: wcsxfrm_l (strxfrm_l.c:679)
> ==139735== by 0x4012A1: main (in /home/slomo/tmp/test/test)
> ==139735== Address 0x4a5c4d0 is 0 bytes inside a block of size 16 alloc'd
> ==139735== at 0x484280F: malloc (vg_replace_malloc.c:442)
> ==139735== by 0x401258: main (in /home/slomo/tmp/test/test)
> ==139735==
This read does not case a page boundary, so overreading is harmless here. This
seems more like a valgrind limitation.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-19 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 11:05 [Bug string/31509] New: " slomo at coaxion dot net
2024-03-19 12:53 ` fweimer at redhat dot com [this message]
2024-03-19 14:06 ` [Bug string/31509] " schwab@linux-m68k.org
2024-03-19 14:12 ` slomo at coaxion dot net
2024-03-19 14:29 ` slomo at coaxion dot net
2024-03-19 14:54 ` fweimer at redhat dot com
2024-03-19 23:21 ` sam at gentoo dot org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31509-131-MMb4JLnYUS@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).