DMAPI dm_getall_disp returns unexpected dispositions

observed on Spectrum Scale 5.1.0 + 5.1.5

For the set of sessions and dispositions:

1. M1 - session which has called dm_set_disp on the global handle to receive mount events

2. F1 - session which has called dm_set_disp on an fs (fs1) during a mount event to start listening for DM_EVENT_READ, DM_EVENT_WRITE and DM_EVENT_TRUNCATE events on the filesystem in question

3. F2 - session which has called dm_set_disp on an fs (fs2) during a mount event to start listening for DM_EVENT_READ, DM_EVENT_WRITE and DM_EVENT_TRUNCATE events on the filesystem in question

while these sessions can be created as above and events are received in the expected places, traversing the disposition information exhibits a number of issues

• dm_getall_disp on the M1 session returns 2 disps (expect 1 for global handle)

  • further, neither of the 2 fshandles contained in the returned dm_dispinfo are the global handle as expected, and calling dm_get_mountinfo on the mounts in question shows info for fs1 and fs2 respectively

• dm_getall_disp on the MWF1 or MWF2 sessions returns EINVAL (expect 1 disp for fs1/fs2 respectively)

Alternatively, with the following session setup:

1. F1 - session which has called dm_set_disp on the global handle to listen for mount events, then set disposition for fs1 during a mount event to start listening for DM_EVENT_READ, DM_EVENT_WRITE and DM_EVENT_TRUNCATE events on the filesystem in question

2. F2 - session which has called dm_set_disp on the global handle to listen for mount events, then set disposition for fs2 during a mount event to start listening for DM_EVENT_READ, DM_EVENT_WRITE and DM_EVENT_TRUNCATE events on the filesystem in question

Traversing the dispositions setup above shows:

• dm_getall_disp on the F1 or F2 sessions returns 2 disps: 1 for each fs (expect 1 dis for fs1/fs2 respectively)

From the above results, it seems that DMAPI is returning all dispositions irrespective of the session ID used to set them where the session used for dm_getall_disp is listening for mount events on the global handle.

Also, but of lesser importance: the documentation suggests that DMAPI should successfully return 0 dispositions rather than failing with EINVAL where the session in question has not set any dispositions