Operational Defect Database

BugZero found this defect 44 days ago.

MongoDB | 2634076

endProcessWithSignal should unblock the signal it's trying to send

Last update date:

4/5/2024

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.

Description:

Info

When we receive a signal while processing another signal (e.g., we segfault while we're constructing a backtrace in response to an abort), we detect that case and try to end the process using the default handler for the second signal (in this example, segfault). The goal is to avoid deadlock by starting our signal handler logic re-entrantly, which may result in it trying to take the MallocFreeOStream lock recursively. However, it can be the case that the signal we're trying to send is blocked. In that case, we will deadlock.

Top User Comments


Steps to Reproduce


Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Open

Learn More

Search:

...