public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pasky at suse dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3313] New: madvise(M_MXFAST,0) sets up a crash Date: Fri, 06 Oct 2006 00:36:00 -0000 [thread overview] Message-ID: <20061006003634.3313.pasky@suse.cz> (raw) When a program calls madvise(M_MXFAST, 0), it will crash the next time it tries to do some memory allocation or get into an infinite loop when it remadvises M_MXFAST to some other value. The problem probably stems from the handling of the first two "unindexable" bins (although I'm not sure right now how are they unindexable) - madvise(M_MXFAST, 0) will set the max_fast to SMALLBIN_WIDTH but fastbin_index(SMALLBIN_WIDTH) == -1, which ain't any good when you use that as an index to the buckets array. -- Summary: madvise(M_MXFAST,0) sets up a crash Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: pasky at suse dot cz CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3313 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-10-06 0:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-06 0:36 pasky at suse dot cz [this message] 2006-10-13 20:54 ` [Bug libc/3313] " drepper at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20061006003634.3313.pasky@suse.cz \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).