Comment 3 for bug 2009595

Some options/considerations to address this (need input from the kernel team),
given there might be impact to (other) userspace tools:

1) Make `linux_banner` like `linux_proc_banner`, i.e., append version signature.

Fixes this issue; expands regression potential to other userspace tools.)

Perhaps this impacts the goal of the patch?

And there's warning quotes on the source, for not doing this. [2]

2) Revert `linux_proc_banner` not to have version signature.

Fixes this issue; reduces regression potential on other userspace tools.

3) Patch `crash` to deal with this

FFixes this isse; keeps regression potential on other userspace tools.

...

[2]

diff --git a/init/version-timestamp.c b/init/version-timestamp.c
...
 /* FIXED STRINGS! Don't touch! */
 const char linux_banner[] =
  "Linux version " UTS_RELEASE " (" LINUX_COMPILE_BY "@"
- LINUX_COMPILE_HOST ") (" LINUX_COMPILER ") " UTS_VERSION "\n";
+ LINUX_COMPILE_HOST ") (" LINUX_COMPILER ") " UTS_VERSION
+#ifdef CONFIG_VERSION_SIGNATURE
+ " (" CONFIG_VERSION_SIGNATURE ")"
+#endif
+ "\n";