-
-
Notifications
You must be signed in to change notification settings - Fork 308
Compute the "safe" distance properly #1801
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
Conversation
The safe pointer that is computed is an exclusive, not inclusive bounds. While we were probably rarely ever bit this, if ever, it still makes sense to apply the limit, properly.
WalkthroughThe changes involve modifications to the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant InflateFast
participant ChunkMemSetSafe
User->>InflateFast: Call inflate_fast()
InflateFast->>ChunkMemSetSafe: Call CHUNKMEMSET_SAFE(params)
ChunkMemSetSafe-->>InflateFast: Memory operation complete
InflateFast-->>User: Return to user
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- inffast_tpl.h (1 hunks)
🔇 Additional comments (1)
inffast_tpl.h (1)
263-263: Approve: Correct adjustment for exclusive boundsThis change aligns with the PR objective of computing the 'safe' distance properly. By removing the
+ 1, theCHUNKMEMSET_SAFEfunction now uses exclusive bounds instead of inclusive ones. This subtle but crucial adjustment enhances the safety of memory operations by preventing potential buffer overruns.The modification is correct and improves the overall robustness of the decompression algorithm.
Dead2
left a comment
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.
LGTM
The safe pointer that is computed is an exclusive, not inclusive bounds. While we were probably rarely ever bit this, if ever, it still makes sense to apply the limit, properly.
Summary by CodeRabbit
Bug Fixes
Documentation