r287723 removed some cleanup from lagg(4), which leads to panics when
changing configuration. Restore the spirit of the code which was removed.
This issue has been refactored out of existence in -HEAD, so this patch is
directly against stable/10.
Details
Details
- Reviewers
hiren darius-dons.net.au - Group Reviewers
Contributor Reviewers (ports) - Commits
- rS294070: [PR 206219] Kernel panic from lagg_ioctl and lagg_port_ioctl
Create and destroy lagg, add and remove ports, switch laggprotos; used to panic, doesn't anymore.
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 2115 Build 2123: arc lint + arc unit
Event Timeline
Comment Actions
Cleanup suggested by @darius-dons.net.au : no need to unlock, when it is immediately locked again.
Comment Actions
Upon further examination, we discovered that some detach routines do
LAGG_WUNLOCK() and some don't. To minimize changes, leave the locking as-is,
and only do the NULLing.
Comment Actions
looks okay to me. I am not sure what was the rationale for removing NULL initializations in the first place. May be @hrs could answer.