Closed
Bug 752293
Opened 13 years ago
Closed 13 years ago
Y'CbCr to RGB ARM asm should mark its stacks non-executable
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
FIXED
mozilla15
People
(Reporter: derf, Assigned: derf)
References
Details
(Keywords: sec-other)
Attachments
(1 file)
836 bytes,
patch
|
glandium
:
review+
|
Details | Diff | Splinter Review |
Bug 671426 identifies several object files that do not indicate support for a non-executable stack. The ARM asm in gfx/ycbcr/yuv_row_arm.s is included in these. This bug is about fixing that asm to request a non-executable stack.
Assignee | ||
Updated•13 years ago
|
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #621391 -
Flags: review?(mh+mozilla)
Comment 2•13 years ago
|
||
Comment on attachment 621391 [details] [diff] [review]
Mark stacks non-executable in yuv_row_arm.s
Review of attachment 621391 [details] [diff] [review]:
-----------------------------------------------------------------
::: gfx/ycbcr/yuv_row_arm.s
@@ +332,5 @@
> .size ScaleYCbCr42xToRGB565_BilinearY_Row_NEON, .-ScaleYCbCr42xToRGB565_BilinearY_Row_NEON
> +
> +#if defined(__ELF__)&&defined(__linux__)
> + .section .note.GNU-stack,"",%progbits
> +#endif
Does that actually work? I thought .s files weren't preprocessed (as opposed to .S files)
Assignee | ||
Comment 3•13 years ago
|
||
(In reply to Mike Hommey [:glandium] from comment #2)
> Does that actually work? I thought .s files weren't preprocessed (as opposed
> to .S files)
Yes it does. They apparently are in our build system (I remember some vague issue with the suffix our automatic rules use that made me use .s instead of .S when I wrote this file, but I don't remember the details).
Status: NEW → ASSIGNED
Updated•13 years ago
|
Attachment #621391 -
Flags: review?(mh+mozilla) → review+
Assignee | ||
Comment 4•13 years ago
|
||
Target Milestone: --- → mozilla15
Comment 5•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•