Wrong usage of data in afr_notify while processing UPCALL evenet

[rafikc30]

Description of problem: The order in which the arguments are sent to the afr_notify and the way they process the arguments while handling UPCALL notifications are wrong. The upcall data has been taken as the xlator_t pointer and stored in the child_xlator local variable and does matching to find the index of the child xlator.

So far both the child_xlator and the index are not used while processing the upcall event, but it could change in the future.

The exact command to reproduce the issue:

The full output of the command that failed:

Expected results:

Mandatory info: - The output of the gluster volume info command:

- The output of the gluster volume status command:

- The output of the gluster volume heal command:

**- Provide logs present on following locations of client and server nodes - /var/log/glusterfs/

**- Is there any crash ? Provide the backtrace and coredump

Additional info:

- The operating system / glusterfs version:

Note: Please hide any confidential data which you don't want to share in public like IP address, file name, hostname or any other configuration

[stale[bot]]

Thank you for your contributions. Noticed that this issue is not having any activity in last ~6 months! We are marking this issue as stale because it has not had recent activity. It will be closed in 2 weeks if no one responds with a comment here.

[stale[bot]]

Closing this issue as there was no update since my last update on issue. If this is an issue which is still valid, feel free to open it.