>
> > +/* Error message for EREMOVE failure, when kernel is about to leak EPC page */
> > +#define EREMOVE_ERROR_MESSAGE \
> > + "EREMOVE returned %d (0x%x), kernel bug likely. EPC page leaked, SGX may become
> > unusuable. Please refer to Documentation/x86/sgx.rst for more information."
>
> Rewritten:
>
> EREMOVE returned %d and an EPC page was leaked; SGX may become unusable.
> This is a kernel bug, refer to Documentation/x86/sgx.rst for more information.
>
> Also please split it across multiple lines.
>
> Paolo
>
Hi Boris/Paolo,
I changed to below (with slight modification on Paolo's):
/* Error message for EREMOVE failure, when kernel is about to leak EPC page */
#define EREMOVE_ERROR_MESSAGE \
"EREMOVE returned %d (0x%x) and an EPC page was leaked. SGX may become unusuable. " \
"This is likely a kernel bug. Refer to Documentation/x86/sgx.rst for more information."
I got a checkpatch warning however:
WARNING: It's generally not useful to have the filename in the file
#60: FILE: Documentation/x86/sgx.rst:223:
+This is likely a kernel bug. Refer to Documentation/x86/sgx.rst for more
I suppose it is OK? Since the error msg is actually hard-coded in the code,
and in this document, IMHO we should explicitly call out what error message user
is supposed to see, when this bug happens, so that user can absolutely know
he/she is dealing with this particular issue.
