Skip to content

HIP: Fix kernel_start null-args handling.#9763

Open
svup-xilinx wants to merge 1 commit intoXilinx:masterfrom
svup-xilinx:HipBugFix01
Open

HIP: Fix kernel_start null-args handling.#9763
svup-xilinx wants to merge 1 commit intoXilinx:masterfrom
svup-xilinx:HipBugFix01

Conversation

@svup-xilinx
Copy link
Copy Markdown
Collaborator

Problem solved by the commit

Add validation in kernel_start constructor to handle null args safely:

Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered

Fixed a null-args validation gap in HIP kernel launch setup: when kernelParams (args) was null, constructor logic could proceed into argument processing for kernels that actually require arguments, which could lead to invalid launch behavior.

How problem was solved, alternative solutions (if any) and why they were rejected

  • If args is null and kernel expects arguments, throw invalid value
  • If args is null and kernel has zero arguments, return early

Risks (if any) associated the changes in the commit

Low

What has been tested and how, request additional testing if necessary

Tested on Windows Strix machine with negative tests of unit tests in testcases-v2 repo.

Documentation impact (if any)

NA

Add validation in kernel_start constructor to handle null args safely:

Fetch kernel argument metadata once
If args is null and kernel expects arguments, throw invalid value
If args is null and kernel has zero arguments, return early
Reuse cached kernel args for argument binding loop

Signed-off-by: Srikanth Vuppala <120363307+svup-xilinx@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown
Contributor

clang-tidy review says "All clean, LGTM! 👍"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant