From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 73473] New: Potential crash bug in src/gallium/auxiliary/rtasm/rtasm_execmem.c
Date: Fri, 10 Jan 2014 13:47:01 +0000 [thread overview]
Message-ID: <bug-73473-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1279 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73473
Priority: medium
Bug ID: 73473
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: Potential crash bug in
src/gallium/auxiliary/rtasm/rtasm_execmem.c
Severity: critical
Classification: Unclassified
OS: Linux (All)
Reporter: jaak-89mTbI93R4uuvFJfX82//w@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Drivers/DRI/nouveau
Product: Mesa
glxgears[4186]: segfault at ffffffffffffffff ip 000078805fc4b901 sp
00007ce9598e21c0 error 7 in nouveau_dri.so[78805f7d1000+136c000]
Stracing it revealed that the crash happens after a mmap(NULL, 10485760,
PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE,MAP_ANONYMOUS, -1, 0) syscall
returns -1.
I think it might be caused by the return value of mmap not being checked in
src/gallium/auxiliary/rtasm/rtasm_execmem.c, leading to the the memory being
accessed somewhere else.
So it probably needs some
if (exec_mem == MAP_FAILED)
check somewhere.
PS: Sorry if this is not the correct component.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2525 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-01-10 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 13:47 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-73473-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-10 14:11 ` [Bug 73473] Potential crash bug in src/gallium/auxiliary/rtasm/rtasm_execmem.c bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-10 15:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-10 18:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-11 10:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-11 12:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-11 13:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-11 13:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-17 19:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-17 23:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-27 13:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-27 13:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-73473-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.