DDK and modular error checking assumes that kernel outlines contain full const info. This allows tools to handle consts at a modular level without needing the whole program or being on the build critical path. (This is how analyzer summaries / DDC works.)

Currently, kernel outlines don't appear to distinguish between a missing constant (?) and a null constant, so DDK builds will trigger unexpected null errors at runtime today.

Possibilities for 2.3:

• Use full kernel files for dependencies instead for now.
• Drop the const-update from 2.3.
• Fix issues around consts in outline.

We're exploring the first for now. If it's not a significant perf regression, it's the easiest path.