check-kernel-fix: Handle missing space between sha and commit title
The commit which caused a regression should be referenced in the format:
Fixes: sha ("title")
But people do mistakes, for example, the commit e769461101377 ("workqueue:
Put the pwq after detaching the rescuer from the pool") contains:
Fixes: 68f83057b913("workqueue: Reap workers via kthread_stop() and remove detach_completion")
As a result, check-kernel-fix fails to find the fixed commit.
Fix the problem by using sed and less strict pattern:
Before:
$> ./scripts/check-kernel-fix CVE-2025-21786
Security fix for CVE-2025-21786 bsc#1238505 with CVSS 5.5
= e76946110137 ("workqueue: Put the pwq after detaching the rescuer from the pool") merged v6.14-rc3~29^2
No Fixes tag. Requires manual review for affected branches.
Link: https://git.kernel.org/linus/e76946110137703c16423baf6ee177b751a34b7e
ACTION NEEDED!
There is no Fixes tag for:
e76946110137 ("workqueue: Put the pwq after detaching the rescuer from the pool")
so we cannot automatically assess which kernel branches require the fix.
After:
$> ./scripts/check-kernel-fix CVE-2025-21786
Security fix for CVE-2025-21786 bsc#1238505 with CVSS 5.5
= e76946110137 ("workqueue: Put the pwq after detaching the rescuer from the pool") merged v6.14-rc3~29^2
Fixes: 68f83057b913 ("workqueue: Reap workers via kthread_stop() and remove detach_completion") merged v6.11-rc1~220^2~20
Link: https://git.kernel.org/linus/e76946110137703c16423baf6ee177b751a34b7e
NO ACTION NEEDED: All relevant branches contain the fix!
Note: Alternative solution with using '(' as another awk delimiter,
e.g. "awk -F '[ \t\n('", is problematic. In this case, awk changes
the semantic and stops ignoring the leading spaces. As a result,
the 'sha' is assigned to either $3 or $2 depending on whether
there are leading spaces or not.
Signed-off-by: Petr Mladek <pmladek@suse.com>