-
Notifications
You must be signed in to change notification settings - Fork 13.4k
[msan] Unpoison indirect outputs for userspace using memset for large operands #79924
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
MaskRay
merged 3 commits into
main
from
users/MaskRay/spr/msan-unpoison-indirect-outputs-for-userspace-using-llvmmemset
Jan 30, 2024
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4552,16 +4552,22 @@ struct MemorySanitizerVisitor : public InstVisitor<MemorySanitizerVisitor> { | |
} | ||
if (!ElemTy->isSized()) | ||
return; | ||
Value *SizeVal = | ||
IRB.CreateTypeSize(MS.IntptrTy, DL.getTypeStoreSize(ElemTy)); | ||
auto Size = DL.getTypeStoreSize(ElemTy); | ||
Value *SizeVal = IRB.CreateTypeSize(MS.IntptrTy, Size); | ||
if (MS.CompileKernel) { | ||
IRB.CreateCall(MS.MsanInstrumentAsmStoreFn, {Operand, SizeVal}); | ||
} else { | ||
// ElemTy, derived from elementtype(), does not encode the alignment of | ||
// the pointer. Conservatively assume that the shadow memory is unaligned. | ||
// When Size is large, avoid StoreInst as it would expand to many | ||
// instructions. | ||
auto [ShadowPtr, _] = | ||
getShadowOriginPtrUserspace(Operand, IRB, IRB.getInt8Ty(), Align(1)); | ||
IRB.CreateAlignedStore(getCleanShadow(ElemTy), ShadowPtr, Align(1)); | ||
if (Size <= 32) | ||
IRB.CreateAlignedStore(getCleanShadow(ElemTy), ShadowPtr, Align(1)); | ||
else | ||
IRB.CreateMemSet(ShadowPtr, ConstantInt::getNullValue(IRB.getInt8Ty()), | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it will hit interceptor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Never mind, we do this all the time here. |
||
SizeVal, Align(1)); | ||
} | ||
} | ||
|
||
|
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe some comment wouldn't hurt here to clarify this constant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bit arbitrary. Perhaps
// The size threshold matches shouldUseBZeroPlusStoresToInitialize for -ftrivial-auto-var-init=zero
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Memset will go into interceptor and do a lot of check, see
__msan_memset
, so it's more expensive than a regular memset. I can't tell what can be optimal constant here, but I would expect something larger. But I doubt it will make a meaningful difference.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your previous comment about the interceptor. The committed patch does contain this description:
"The intrinsic, if lowered to libcall, will use the msan interceptor."
Inline asm isn't commonly used:) This patch is for
=m
in extended asm, which I believe is more uncommon, and if used, usually with small objects. I guess 32 and 64 won't make a difference.