Skip to content

fix(ramshared): guard clauses for request queue initialization parameters - #1904

Closed
emersonbusson wants to merge 4 commits into
mainfrom
fix-ramshared-queue-init-1754927304022925084
Closed

emersonbusson wants to merge 4 commits into
mainfrom
fix-ramshared-queue-init-1754927304022925084

Conversation

@emersonbusson

Copy link
Copy Markdown
Owner

Summary

Refactor ramshared_queue_init to validate queue depth and device pointer non-nullness with early guard returns, replacing clamp_t logic with strict boundary validation returning -EINVAL for invalid parameters, meeting architecture guidelines.

Commits

SHA Details
ed3d735
DetailsFiles: drivers/block/ramshared/queue.c
Validation: CI scripts
Risk/rollback: Revert if q_depth values fail init

Issue

N/A

Owner

jules

Labels

type:bug, area:kernel

Validation

Checkpatch, style scripts, and ABI guards.

Rollback trigger

If the driver fails to initialize queues with legitimate q_depth values, revert this commit.


PR created automatically by Jules for task 1754927304022925084 started by @emersonbusson

…ters

Refactor ramshared_queue_init to validate queue depth and device
pointer non-nullness with early guard returns, replacing
clamp_t logic with strict boundary validation returning
-EINVAL for invalid parameters, meeting architecture guidelines.

Rollback trigger: If the driver fails to initialize queues with
legitimate q_depth values, revert this commit.
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

…ters

Refactor ramshared_queue_init to validate queue depth and device
pointer non-nullness with early guard returns, replacing
clamp_t logic with strict boundary validation returning
-EINVAL for invalid parameters, meeting architecture guidelines.

Rollback trigger: If the driver fails to initialize queues with
legitimate q_depth values, revert this commit.
…ters

Refactor ramshared_queue_init to validate queue depth and device
pointer non-nullness with early guard returns, replacing
clamp_t logic with strict boundary validation returning
-EINVAL for invalid parameters, meeting architecture guidelines.

Rollback trigger: If the driver fails to initialize queues with
legitimate q_depth values, revert this commit.
…ters

Refactor ramshared_queue_init to validate queue depth and device
pointer non-nullness with early guard returns, replacing
clamp_t logic with strict boundary validation returning
-EINVAL for invalid parameters, meeting architecture guidelines.

Rollback trigger: If the driver fails to initialize queues with
legitimate q_depth values, revert this commit.
@emersonbusson

Copy link
Copy Markdown
Owner Author

Closed in favor of PR #2085 consolidation.

@emersonbusson
emersonbusson deleted the fix-ramshared-queue-init-1754927304022925084 branch September 23, 2026 15:04
@google-labs-jules

Copy link
Copy Markdown

Closed in favor of PR #2085 consolidation.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.

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