Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66368

Don't call LOGV2 in the boost logging exception handler

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • Security 2022-06-27

    Description

      Since boost logging exceptions may occur during doLogImpl, this has the potential to re-enter doLogImpl, which is decidedly not reentry-safe. A couple of possible solutions:

      • Add the log entry to a queue, which is popped by some forever-running handler thread.
      • Don't log, and instead output the log message to stderr.

      Attachments

        Issue Links

          Activity

            People

              sergey.galtsev@mongodb.com Sergey Galtsev
              gabriel.marks@mongodb.com Gabriel Marks
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: