We do not want more than one dump to be triggered causing memory issues. As part of testing multiple user initiated dump are triggered as dump collection is done in aync manner the caller thread is not blocked allowing user to triggern N no of dumps in the end causing system to go into undefined state.
At present added a flag to check if dump is in progress and rejecting other dumps but it would be good if we have a type in the dump which can identify it the dump is of user initiated.
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/51219/6/dump_manager_bmc.hpp
We do not want more than one dump to be triggered causing memory issues. As part of testing multiple user initiated dump are triggered as dump collection is done in aync manner the caller thread is not blocked allowing user to triggern N no of dumps in the end causing system to go into undefined state.
At present added a flag to check if dump is in progress and rejecting other dumps but it would be good if we have a type in the dump which can identify it the dump is of user initiated.
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-debug-collector/+/51219/6/dump_manager_bmc.hpp