On Tue, Aug 17, 2021 at 1:30 PM Dilip Kumar <dilipbal...@gmail.com> wrote: > > On Tue, Aug 17, 2021 at 10:54 AM Amit Kapila <amit.kapil...@gmail.com> wrote: > > > > > 5. How can we provide a strict mechanism to not allow to use dsm APIs > > for non-dsm FileSet? One idea could be that we can have a variable > > (probably bool) in SharedFileSet structure which will be initialized > > in SharedFileSetInit based on whether the caller has provided dsm > > segment. Then in other DSM-based APIs, we can check if it is used for > > the wrong type. > > Yeah, we can do something like that, can't we just use an existing > variable instead of adding new, e.g. refcnt is required only when > multiple processes are attached, so maybe if dsm segment is not passed > then we can keep refcnt as 0 and based on we can give an error. For > example, if we try to call SharedFileSetAttach for the SharedFileSet > which has refcnt as 0 then we error out? >
But as of now, we treat refcnt as 0 for SharedFileSet that is already destroyed. See SharedFileSetAttach. -- With Regards, Amit Kapila.
