drivers: pci: Fix endpoint null guard logic#19331
Closed
Old-Ding wants to merge 0 commit into
Closed
Conversation
xiaoxiang781216
previously approved these changes
Jul 6, 2026
Contributor
|
@Old-Ding please fix the conflict. |
acassis
previously approved these changes
Jul 6, 2026
Contributor
|
@Old-Ding please fix conflicts |
cba5969
89e3825 to
cba5969
Compare
cba5969 to
1fc6f2b
Compare
Contributor
|
@Old-Ding why did you close it? |
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
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.
Summary
Rationale
The existing guard expressions used && or || in a way that could dereference a null pointer while evaluating the guard itself. The fixed checks follow the surrounding PCI endpoint guard style and keep the validation at the call boundary.
Testing