refactor(ramshared): linearize pci_remove teardown sequence - #1891
emersonbusson wants to merge 4 commits into
Conversation
Rollback trigger: Kernel panics on device remove or memory leak reports from KASAN.
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Rollback trigger: Kernel panics on device remove or memory leak reports from KASAN.
Rollback trigger: Kernel panics on device remove or memory leak reports from KASAN.
Rollback trigger: Kernel panics on device remove or memory leak reports from KASAN.
|
Closed in favor of PR #2085 consolidation. |
Understood. Acknowledging that this work is now obsolete and stopping work on this task. |
Resumo
Linearized
ramshared_pci_removeby validatingrs_devwith a clear kernel error on missing data and performing strictly reversed teardown order:pci_set_drvdata, queues, DMA, master, regions, disable, and mutex destroy.Commits
Details
Details
Details
Issue
Task: linearize pci_remove teardown sequence with guard checks
Owner
jules
Labels
type:refactor area:kernel-linux
Validacao
Visually validated C logic strictly respects reverse sequence requirement. Tested struct and pointer safety.
Rollback trigger
Kernel panics on device remove or memory leak reports from KASAN.
PR created automatically by Jules for task 9252804470000937126 started by @emersonbusson