public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bruno at clisp dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30584] New: initstate and initstate_r crash when the state argument is unaligned Date: Sun, 25 Jun 2023 15:52:14 +0000 [thread overview] Message-ID: <bug-30584-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30584 Bug ID: 30584 Summary: initstate and initstate_r crash when the state argument is unaligned Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: bruno at clisp dot org CC: drepper.fsp at gmail dot com Target Milestone: --- Created attachment 14947 --> https://sourceware.org/bugzilla/attachment.cgi?id=14947&action=edit test case foo1.c On Linux/SPARC (both in 64-bit mode and in 32-bit mode), the initstate() and initstate_r() functions crash when the state argument is unaligned. The specification of initstate() in https://pubs.opengroup.org/onlinepubs/9699919799/functions/initstate.html and the documentation of initstate() and initstate_r() in https://www.gnu.org/software/libc/manual/html_node/BSD-Random.html require merely a byte array. So, passing an aligned byte array (of size 128 or more) is allowed. How to reproduce: Remote login to cfarm105.cfarm.net. $ gcc -Wall foo1.c $ ./a.out Bus error $ gcc -m32 -Wall foo1.c $ ./a.out Bus error $ gcc -Wall foo2.c $ ./a.out Bus error $ gcc -m32 -Wall foo2.c $ ./a.out Bus error -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-06-25 15:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-25 15:52 bruno at clisp dot org [this message] 2023-06-25 15:52 ` [Bug libc/30584] " bruno at clisp dot org 2023-06-25 15:53 ` bruno at clisp dot org 2023-06-25 15:54 ` bruno at clisp dot org 2023-06-25 23:38 ` ppluzhnikov at google dot com 2023-07-04 9:41 ` schwab@linux-m68k.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-30584-131@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: linkBe 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).