Crash in [@ setup_stack_prot] caused by a madvise() call
Categories
(Core :: Security: Process Sandboxing, defect, P1)
Tracking
()
People
(Reporter: gsvelto, Assigned: jld)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
Crash report: https://crash-stats.mozilla.org/report/index/79f6d944-3507-4f79-8986-aec210250226
Reason:
SIGSYS / SYS_SECCOMP
Top 10 frames:
0 libc.so.6 __GI_madvise /usr/src/debug/glibc-2.41.9000-1.fc43.x86_64/sysdeps/unix/syscall-template.S:117
1 libc.so.6 setup_stack_prot /usr/src/debug/glibc-2.41.9000-1.fc43.x86_64/nptl/allocatestack.c:203
1 libc.so.6 allocate_stack /usr/src/debug/glibc-2.41.9000-1.fc43.x86_64/nptl/allocatestack.c:519
1 libc.so.6 __pthread_create_2_1 /usr/src/debug/glibc-2.41.9000-1.fc43.x86_64/nptl/pthread_create.c:660
2 firefox-bin pthread_create mozglue/interposers/pthread_create_interposer.cpp:99
3 libnspr4.so _PR_CreateThread nsprpub/pr/src/pthreads/ptthread.c:429
4 libnspr4.so PR_CreateThread nsprpub/pr/src/pthreads/ptthread.c:496
5 libxul.so nsThread::Init(nsTSubstring<char> const&) xpcom/threads/nsThread.cpp:615
6 libxul.so nsThreadManager::NewNamedThread(nsTSubstring<char> const&, nsIThreadManager::... xpcom/threads/nsThreadManager.cpp:619
7 libxul.so NS_NewNamedThread(nsTSubstring<char> const&, nsIThread**, already_AddRefed<ns... xpcom/threads/nsThreadUtils.cpp:176
This is caused by a madvise()
call that was introduced by this glibc change.
Comment 1•28 days ago
|
||
Huge spike in Nightly crashes, probably worth release tracking.
Assignee | ||
Comment 2•28 days ago
•
|
||
It looks like this currently applies only to Fedora Rawhide, their rolling-release experimental distro which uses bleeding-edge prerelease versions of glibc.
Also, this crash is Nightly-only; other branches will return an error and glibc will fall back to mprotect
.
(Edit: fixed hyperlink)
Updated•27 days ago
|
Updated•27 days ago
|
Assignee | ||
Comment 4•25 days ago
|
||
Comment 6•22 days ago
|
||
bugherder |
Comment 7•21 days ago
|
||
The patch landed in nightly and beta is affected.
:jld, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox137
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 8•20 days ago
|
||
137 is unaffected now that it's Beta; the crash is Nightly-only.
Updated•19 days ago
|
Updated•19 days ago
|
Description
•