Hi chromium-dev,
TL;DR: We are initiating a large-scale mechanical conversion from DCHECKs to CHECKs in primarily browser focused code directories. This is to improve Chrome's memory safety in production focused mainly on browser process side CHECKs (~26,000 DCHECKs).
Background & Motivation:
Multiple long-standing, high-severity vulnerabilities have recently been uncovered by an LLM-based tool (project fortify), and we found that some of them could have been mitigated if the invariant conditions of DCHECKs had been enforced in production. The hope is by hardening others more widely we can prevent discovering more in future.
This has been reviewed by the technical steering council, as well as other stakeholders, and approved for LSC and will start in M154.
Here is an explainer doc.
The target directories are:
//chrome/browser/
//chromecast/media/
//components/cast_streaming/
//content/browser/
//media/mojo/services/
//ui/
Action requested:
- No action requested.
- If and only if you have a concern about the conversion, you can opt-out of the mechanical conversion by adding the CHECK-exclusion: comment to each DCHECK (a TODO comment is not mandatory, it's optional).
Cheers,
Yuki Shiino
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAN0uC_R6i0T%2BmCWPY5jqYBNVOqeV_iWLAHGQHCbSER9ao413ig%40mail.gmail.com.
