If both DataSectionObject and ImageSectionObject exist, it appears
that the intentional behavior of MmForceSectionClosed is to "only act
against ImageSectionObject." How can I most intelligently add the
DeleteOnClose flag to the DataSectionObject, at a time when the
ImageSectionObject also exists?
The intention is as you might expect; to get IRP_MJ_CLOSE as soon as
the reference counts from the mappings hit zero. Something a call to
MmForceSectionClosed is successfully achieving when only one or the
other of the sections exist, but not when both exist at the same time.
Client for Open Enterprise Server