From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 73473] Potential crash bug in src/gallium/auxiliary/rtasm/rtasm_execmem.c
Date: Mon, 27 Jan 2014 13:24:49 +0000 [thread overview]
Message-ID: <bug-73473-8800-UXYgo4JrbO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73473-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 881 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73473
--- Comment #10 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Yay the crash should happen no more
commit 4dd445f1cf80292f10eda53665cefc2a674d838d
Author: Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Fri Jan 10 18:00:17 2014 +0000
gallium/rtasm: handle mmap failures appropriately
For a variety of reasons mmap (selinux and pax to name
a few) and can fail and with current code. This will
result in a crash in the driver, if not worse.
This has been the case since the inception of the
gallium copy of rtasm.
Cc: 9.1 9.2 10.0 <mesa-stable-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=73473
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1908 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 prev parent reply other threads:[~2014-01-27 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 13:47 [Bug 73473] New: Potential crash bug in src/gallium/auxiliary/rtasm/rtasm_execmem.c bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-73473-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-01-10 14:11 ` [Bug 73473] " 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 [this message]
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-UXYgo4JrbO@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.