CODING_STYLE: Document how to handle unexpected conditions
authorGeorge Dunlap <george.dunlap@citrix.com>
Mon, 9 Dec 2019 11:12:07 +0000 (11:12 +0000)
committerGeorge Dunlap <george.dunlap@citrix.com>
Mon, 13 Jan 2020 13:40:03 +0000 (13:40 +0000)
commit03bfe526ecadc86f31eda433b91dc90be0563919
tree280eb79c24e7b8fe1218d4c29b6c88049d00c1cf
parent8842d01b300919e20bca2e1138c458a8483600f8
CODING_STYLE: Document how to handle unexpected conditions

It's not always clear what the best way is to handle unexpected
conditions: whether with ASSERT(), domain_crash(), BUG_ON(), or some
other method.  All methods have a risk of introducing security
vulnerabilities and unnecessary instabilities to production systems.

Provide guidelines for different options and when to use them.

Signed-off-by: George Dunlap <george.dunlap@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Julien Grall <julien@xen.org>
CODING_STYLE