Move an assignment, drop a label, and change gotos to break statements in vm_map_unwire. The code generated on amd86 is unchanged.
Details
Details
Diff Detail
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
Comment Actions
I don't like this change. In cases like this, specifically error handling in complex code, the goto is easier to understand (and very common in kernel code). A "break;" is context sensitive, i.e., I have to determine whether I am a nested loop.
Comment Actions
Typically, when there is some kind of dispute over a change, it is appropriate to revert the change pending some discussion, especially if the dispute is with a maintainer of the code in question. If you feel strongly that the change should be kept, it would be reasonable to continue that discussion here following a revert.
Comment Actions
I don't feel strongly enough about this issue to request that the change be reverted.