Bug 265853 - freebsd-update(8): new kernel produces pretty different what(1)'s output
Summary: freebsd-update(8): new kernel produces pretty different what(1)'s output
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 13.1-RELEASE
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-15 10:04 UTC by Vinícius Zavam
Modified: 2022-12-14 17:09 UTC (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vinícius Zavam freebsd_committer freebsd_triage 2022-08-15 10:04:44 UTC 
ISSUE:

  after updating 13.1-RELEASE to 13.1-RELEASE-p1 using freebsd-update(8), the output produced by what(1) is pretty different and does not present the proper branch and git revision as in old 13.1-RELEASE's kernel.

HOW TO REPRODUCE:

  0. install a vanilla FreeBSD 13.1-RELEASE machine;
  1. check the output of `what -qs /boot/kernel/kernel` before updating your system;
  2. update the base system using `freebsd-update fetch install`
  3. reboot the machine (because a new kernel was installed);
  4. check that output of step 1. again.

user23lab9@freebsd:~ % freebsd-version -kru
13.1-RELEASE-p1
13.1-RELEASE-p1
13.1-RELEASE-p1

user23lab9@freebsd:~ % what -qs /boot/kernel/kernel
FreeBSD 13.1-RELEASE-p1 GENERIC

user23lab9@freebsd:~ % what -qs /boot/kernel.old/kernel
FreeBSD 13.1-RELEASE releng/13.1-n250148-fc952ac2212 GENERIC

user23lab9@freebsd:~ % uname -abiUK
FreeBSD freebsd.kvm.localdomain 13.1-RELEASE-p1 FreeBSD 13.1-RELEASE-p1 GENERIC amd64 GENERIC 1301000 1301000 5899e32947db26168b53c075c51ae45e0773bb12

IMPACT:

  this is, AFAIK, affecting *all* users of freebsd-update(8).
Comment 1 Vinícius Zavam freebsd_committer freebsd_triage 2022-08-15 10:06:55 UTC 
SEE ALSO:

  * https://lists.freebsd.org/pipermail/freebsd-reproducibility/2020-April/000003.html (not really sure if that's directly related?)
Comment 2 Ed Maste freebsd_committer freebsd_triage 2022-08-15 14:43:01 UTC 
As far as I can tell this has happened for each release in the past, between the original release and -p1. Although undesired I believe it is not a regression. It should be addressed by future changes to the way updates are built.