panic in vnode_valid_pn
When the wad for 8376 was put together, one of the necessary changes, OS-3991, was accidentally skipped. Without this, there are certain code paths in vnode_valid_pn which result in faults. This fix should be included to round out the v_path work.
Thanks to Yuri for reporting the issue and assisting with troubleshooting.
The stack often looks something like this:
ffffff00202e8bf0 vn_rele+0x13(1) ffffff00202e8ca0 vnode_valid_pn+0x1da(ffffff3152b44000, ffffff070dd6b800, ffffff00202e8d00, ffffff00202e8ce0, 10, ffffff0718b54900) ffffff00202e8d90 vnodetopath_common+0x149(0, ffffff3152b44000, ffffff9b8984f7c0, 400, ffffff0718b54900, 10) ffffff00202e8e60 dogetcwd+0x1e1(ffffff9b8984f7c0, 400) ffffff00202e8eb0 getcwd+0x80(8045ae3, 400) ffffff00202e8f00 _sys_sysenter_post_swapgs+0x237()
Updated by Electric Monk about 3 years ago
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
commit 8902f61a33bdc50fa8815c0a787c286591fe12ef Author: Patrick Mooney <firstname.lastname@example.org> Date: 2017-06-30T15:56:18.000Z 8438 panic in vnode_valid_pn Reviewed by: Jerry Jelinek <email@example.com> Reviewed by: Yuri Pankov <firstname.lastname@example.org> Reviewed by: Robert Mustacchi <email@example.com> Approved by: Gordon Ross <firstname.lastname@example.org>