An Ubuntu kernel bug causes container crashes

I suppose that you might be able to generate metadata for a piece of software in the form of a directed acyclic graph representing a kind of causality or dependency. Something that touches one branch isn't blocked by something on another branch, but something upstream blocks downstream patches due to changed downstream-visible behavior. With language fine-tuning you could manage what does and does not cause a downstream-visible change of behavior, and what behavior precisely a patch depends on. Dunno whether most software lends itself to a good directed acyclic graph of behavior causality though.