Public bug reported:
SRU Justification
Impact: The fix for bug 1852581 causes the build log to be spammed with
"/bin/bash: line 5: warning: command substitution: ignored null byte in
input" each time an unsigned module is processed.
Fix: Replace the fix with a different one which does not result in the
message.
Test Case: Build with debug package build enabled, and check for the
message in the logs. Also confirm that the resulting modules are signed,
aside from those in staging and not whitelisted in drivers/staging
/signature-inclusion.
Regression Potential: I've tested the patch for the above criteria, and
all is working as expected, so this should not result in any
regressions.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Affects: linux (Ubuntu Eoan)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853843
Title:
Kerne build log filled with "/bin/bash: line 5: warning: command
substitution: ignored null byte in input"
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
SRU Justification
Impact: The fix for bug 1852581 causes the build log to be spammed
with "/bin/bash: line 5: warning: command substitution: ignored null
byte in input" each time an unsigned module is processed.
Fix: Replace the fix with a different one which does not result in the
message.
Test Case: Build with debug package build enabled, and check for the
message in the logs. Also confirm that the resulting modules are
signed, aside from those in staging and not whitelisted in
drivers/staging/signature-inclusion.
Regression Potential: I've tested the patch for the above criteria,
and all is working as expected, so this should not result in any
regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853843/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
