moved dnode has incorrect dn_next_type
While investigating a different problem, I noticed that moved dnodes (those processed by dnode_move_impl() via kmem_move()) have an incorrect dn_next_type.
This could cause the on-disk dn_type to be changed to an invalid value.
dn_moved = 0x1
dn_next_type = [ 0xfe, 0xca, 0xdd, 0 ]
The fix to copy the dn_next_type in dnode_move_impl().
Updated by Electric Monk over 1 year ago
- % Done changed from 0 to 100
- Status changed from New to Closed
commit c7fbe46df966ea665df63b6e6071808987e839d1 Author: Matthew Ahrens <firstname.lastname@example.org> Date: 2018-06-19T19:28:37.000Z 9338 moved dnode has incorrect dn_next_type Reviewed by: Prashanth Sreenivasa <email@example.com> Reviewed by: Serapheim Dimitropoulos <firstname.lastname@example.org> Reviewed by: Dan Kimmel <email@example.com> Approved by: Robert Mustacchi <firstname.lastname@example.org>