Open
Conversation
yunwei37
force-pushed
the
master
branch
3 times, most recently
from
1354316 to
a6a132b
Compare
Contributor
There was a problem hiding this comment.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (2)
runtime/src/bpftime_shm.cpp:576
- The change removes the shift and mask logic used to represent a pointer. Please verify that all consumers of map_ptr_by_fd and map_val expect the file descriptor directly and that this change does not introduce unintended behavior.
return fd;
runtime/src/bpf_map/userspace/map_in_maps.hpp:29
- The direct cast of map_id to a pointer replaces the previous shifting logic. Confirm that this change is consistent with how map pointer values are interpreted throughout the codebase.
return (void *)((u_int64_t)map_id);
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 8730391 | Triggered | Generic Private Key | 872ff64 | benchmark/deepflow/go-server/key.pem | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
yunwei37
force-pushed
the
master
branch
2 times, most recently
from
cbcb1e9 to
20acd88
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
The old version shift 32 bit in map_by_fd, we don't need to do that.