Skip to content

CDO: Introduce log_error()#1456

Merged
joe-lawrence merged 1 commit intodynup:masterfrom
liu-song-6:log_error
May 14, 2025
Merged

CDO: Introduce log_error()#1456
joe-lawrence merged 1 commit intodynup:masterfrom
liu-song-6:log_error

Conversation

@liu-song-6
Copy link
Copy Markdown
Contributor

log_normal() is used in some critical errors, such as:

"changed section XXXX not selected for inclusion".

It is not very obvious this is a fatal error.

Introduce log_error() and use it for critical messages.

Note that we are not using ERROR() here, because ERROR() will terminate CDO immediately, which is not the desired behavior.

Copy link
Copy Markdown
Contributor

@joe-lawrence joe-lawrence left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable. On a related note, too bad there are so many existing ERROR() calls, otherwise we should have called it FATAL() or something to indicate that it means business and will halt the program :)

log_normal() is used in some critical errors, such as:

"changed section XXXX not selected for inclusion".

It is not very obvious this is a fatal error.

Introduce log_error() and use it for critical messages.

Note that we are not using ERROR() here, because ERROR() will terminate
CDO immediately, which is not the desired behavior.

Signed-off-by: Song Liu <song@kernel.org>
Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com> [merge conflict]
@joe-lawrence
Copy link
Copy Markdown
Contributor

(The latest two CDO MRs both touch kpatch_verify_patchability(), so I quickly rebased this one to smooth over the merge conflict.)

@joe-lawrence joe-lawrence merged commit e4799a8 into dynup:master May 14, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants