RHEL-185213: [Balloon] Remove dead ASSERT - #1619
Conversation
Signed-off-by: Harshal Patil <harshapa@redhat.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe change removes the host acknowledgment success assertion in ChangesBalloon acknowledgment handling
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This PR removes a dead assertion without changing balloon runtime behavior, so no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
ok to test |
KeWaitForSingleObject returns 4 possible statuses:
STATUS_SUCCESS - possible
STATUS_TIMEOUT - possible
STATUS_ALERTED - Alertable is set to FALSE so not possible
STATUS_USER_APC - Alertable is set to FALSE and the parameter is KernelMode instead of UserMode so again not possible
The ASSERT is defined in ntifs.h, balloon code does not redefine it. So in release builds it is harmless anyway. But in debug builds, NT_SUCCESS(STATUS_TIMEOUT) and NT_SUCCESS(STATUS_SUCCESS) both will be true. So ASSERT seems to be dead code here, we can remove it entirely.
Reference: KeWaitForSingleObject function (wdm.h) - Windows drivers
Summary by CodeRabbit