dlm: use __le types for rcom messages
authorAlexander Aring <aahringo@redhat.com>
Mon, 4 Apr 2022 20:06:40 +0000 (16:06 -0400)
committerDavid Teigland <teigland@redhat.com>
Wed, 6 Apr 2022 19:02:32 +0000 (14:02 -0500)
commit2f9dbeda8dc04b5b754e032000adf6bab03aa9be
tree4c8b8c0550999d436bebd219b6e2afad4edc0c98
parent3428785a65dabf05bc899b6c5334984e98286184
dlm: use __le types for rcom messages

This patch changes to use __le types directly in the dlm rcom
structure which is casted at the right dlm message buffer positions.

The main goal what is reached here is to remove sparse warnings
regarding to host to little byte order conversion or vice versa. Leaving
those sparse issues ignored and always do it in out/in functionality
tends to leave it unknown in which byte order the variable is being
handled.

Signed-off-by: Alexander Aring <aahringo@redhat.com>
Signed-off-by: David Teigland <teigland@redhat.com>
fs/dlm/dlm_internal.h
fs/dlm/lock.c
fs/dlm/member.c
fs/dlm/rcom.c
fs/dlm/recover.c
fs/dlm/util.c
fs/dlm/util.h