Re: [Xen-devel] [PATCH] CODING_STYLE: Document how to handle unexpected conditions

2020-01-07 Thread Julien Grall
Hi George, On 07/01/2020 12:02, George Dunlap wrote: 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

Re: [Xen-devel] [PATCH] CODING_STYLE: Document how to handle unexpected conditions

2020-01-07 Thread Jan Beulich
On 07.01.2020 13:02, George Dunlap wrote: > 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

Re: [Xen-devel] [PATCH] CODING_STYLE: Document how to handle unexpected conditions

2020-01-07 Thread George Dunlap
On 1/7/20 12:02 PM, George Dunlap wrote: > 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

[Xen-devel] [PATCH] CODING_STYLE: Document how to handle unexpected conditions

2020-01-07 Thread George Dunlap
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