On 10/04/2019 16:24, Nikolay Borisov wrote: > The only possible 'private_data' that is passed to this function is > actually an inode. Make that explicit by changing the signature of the > call back. No functional changes. Can't we change struct extent_io_tree::private_data and extent_io_tree_init(..., void *private_data) to be an inode as well? If I didn't overlook something we always pass in an inode or NULL. -- Johannes Thumshirn SUSE Labs Filesystems jthumshirn@xxxxxxx +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
