[sanitizer] Suggest checking ulimit -d in addition to ulimit -v #98625
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since Linux 4.7, RLIMIT_DATA may result in mmap() returning ENOMEM.
Example:
$ clang -fsanitize=address -o hello hello.c
$ ulimit -d 100000
$ ./hello
==3349007==ERROR: AddressSanitizer failed to allocate 0x10000000 (268435456) bytes at address 7fff7000 (errno: 12)
==3349007==ReserveShadowMemoryRange failed while trying to map 0x10000000 bytes. Perhaps you're using ulimit -v
Suggest checking ulimit -d in addition to ulimit -v.
Member
|
@llvm/pr-subscribers-compiler-rt-sanitizer Author: Ilya Leoshkevich (iii-i) ChangesSince Linux 4.7, RLIMIT_DATA may result in mmap() returning ENOMEM. Example: Suggest checking ulimit -d in addition to ulimit -v. Full diff: https://github.com/llvm/llvm-project/pull/98625.diff 1 Files Affected:
diff --git a/compiler-rt/lib/sanitizer_common/sanitizer_common_libcdep.cpp b/compiler-rt/lib/sanitizer_common/sanitizer_common_libcdep.cpp
index a174ae7be991d..3966d82d51ee9 100644
--- a/compiler-rt/lib/sanitizer_common/sanitizer_common_libcdep.cpp
+++ b/compiler-rt/lib/sanitizer_common/sanitizer_common_libcdep.cpp
@@ -169,7 +169,7 @@ void ReserveShadowMemoryRange(uptr beg, uptr end, const char *name,
: !MmapFixedNoReserve(beg, size, name)) {
Report(
"ReserveShadowMemoryRange failed while trying to map 0x%zx bytes. "
- "Perhaps you're using ulimit -v\n",
+ "Perhaps you're using ulimit -v or ulimit -d\n",
size);
Abort();
}
|
vitalybuka
reviewed
Jul 12, 2024
| Report( | ||
| "ReserveShadowMemoryRange failed while trying to map 0x%zx bytes. " | ||
| "Perhaps you're using ulimit -v\n", | ||
| "Perhaps you're using ulimit -v or ulimit -d\n", |
Collaborator
There was a problem hiding this comment.
should not this relevant only to !madvise_shadow case?
vitalybuka
approved these changes
Jul 12, 2024
aaryanshukla
pushed a commit
to aaryanshukla/llvm-project
that referenced
this pull request
Jul 14, 2024
…#98625) Since Linux 4.7, RLIMIT_DATA may result in mmap() returning ENOMEM. Example: $ clang -fsanitize=address -o hello hello.c $ ulimit -d 100000 $ ./hello ==3349007==ERROR: AddressSanitizer failed to allocate 0x10000000 (268435456) bytes at address 7fff7000 (errno: 12) ==3349007==ReserveShadowMemoryRange failed while trying to map 0x10000000 bytes. Perhaps you're using ulimit -v Suggest checking ulimit -d in addition to ulimit -v.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Linux 4.7, RLIMIT_DATA may result in mmap() returning ENOMEM. Example:
Suggest checking ulimit -d in addition to ulimit -v.