Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Feb 2021 23:21:34 -0800
From:      Mark Millard <marklmi@yahoo.com>
To:        Warner Losh <imp@bsdimp.com>, freebsd-stable@freebsd.org
Cc:        Kevin Oberman <rkoberman@gmail.com>, karl@denninger.net, Ed Maste <emaste@freebsd.org>
Subject:   Re: How do I know if my 13-stable has security patches?
Message-ID:  <B105E09A-B2E4-4249-86A5-C64CCDEDEDEF@yahoo.com>
References:  <B105E09A-B2E4-4249-86A5-C64CCDEDEDEF.ref@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh imp at bsdimp.com wrote on
Fri Feb 26 00:23:15 UTC 2021 :

> Before I get into the blow by blow (which can sound nit-picky, despite =
my
> best efforts), I would like to apologize. It wasn't completely =
appreciated
> how clearly the dependencies that the nXXXXX number being generated =
needed
> to be communicated. And for that I apologize. When they are met, we =
have
> all the pieces we need to at build time to generate the nXXXXX number =
and
> none of the fallback methods are needed. I'll work to update the docs =
to
> clearly communicate this since it is completely absent from my current =
docs.
. . . (lots more later and in earlier notices) . . .

There is a fairly simple technique to figure out the relationships
based on using https://cgit.freebsd.org instead of a local .git
copy.

I'll give examples based on the notice's:

releng/13.0/                     =
ce9af53d0897a1cb926bd244f499fc09b1626b27

and examples of before (earlier date/time) and after (later
date/time), presumably from some command like uname -apKU .

The date/time-increasing order for the below is (for reference):
8305d6906fe983a . . . ce9af53d0897a1c . . . ba27dd8be821792

I'll follow the same steps with the before value vs. the
after value substituted and report what results.

I go to: https://cgit.freebsd.org/src/log/?h=3Dreleng/13.0
to match that part of the notice. (I'm not trying to specify
which technique that one uses for this, just the result.)

I select range and enter: 8305d6906fe983a~1..ce9af53d0897a1c
(8305d6906fe983a happens to be a before ce9af53d0897a1c value):

(Spacing in the ranges seems to be important to avoid.)

The result is I see:

Commit message (Expand)	Author	Age	Files	Lines

(In other words an empty output/range meets the criteria
for when uname -apKU reported an earlier date/time's
commit.)

By contrast . . .

I again go to: https://cgit.freebsd.org/src/log/?h=3Dreleng/13.0 .

I select range and enter: ba27dd8be821792~1..ce9af53d0897a1c
(ba27dd8be821792 happens to be an after ce9af53d0897a1c value):

Commit message (Expand)	Author	Age	Files	Lines
*   	zfs: merge OpenZFS master-9312e0fd1	Martin Matuska	4 days	=
40	-248/+724
|\  =09
| * 	Update vendor/openzfs to master-9312e0fd1vendor/openzfs	Martin =
Matuska	4 days	36	-247/+716
* | 	Fix build after 2c7dc6bae9fd.	Alexander Motin	4 days	1	=
-0/+4
* | 	Refactor CTL datamove KPI.	Alexander Motin	4 days	12	=
-162/+94
* | 	jail: Add pr_state to struct prison	Jamie Gritton	4 days	=
2	-51/+65
* | 	vfs: shrink struct vnode to 448 bytes on LP64	Mateusz Guzik	=
4 days	1	-1/+12
* | 	jail: fix build after the previous commit	Mateusz Guzik	=
4 days	1	-1/+1
* | 	jail: Change the locking around pr_ref and pr_uref	Jamie =
Gritton	4 days	6	-235/+232
* | 	sctp: improve computation of an alternate net	Michael Tuexen	=
5 days	1	-36/+49
* | 	sctp: clear a pointer to a net which will be removed	Michael =
Tuexen	5 days	1	-0/+4
* | 	ext2fs: clear write cluster tracking on truncation	=
Konstantin Belousov	5 days	1	-0/+1
. . . (goes on indefinately) . . .

In other words it starts to list everything at
ba27dd8be821792 or before (in time) for the branch.
(Listing ba27dd8be821792 itself is why I use the ~1
part of the notation on the left hand hash-id.)

(In other words a non-empty output/range meets the
criteria for when uname -apKU reported a no-earlier
date/time's commit, normally a later date/time's
commit.)

So the empty vs. non-empty result indicates the time
relationship of the hash-ids on the branch.

No need for a local .git of any kind but access to
https://cgit.freebsd.org is needed for the technique.


Notes:

The order of the range specifications is deliberate
in order to make the output harder to misinterpret.
This is because . . .

Using: ce9af53d0897a1c~1..8305d6906fe983a
gives:

Commit message (Expand)	Author	Age	Files	Lines
* 	loader: unload command should reset tg_kernel_supported in =
gfx_state	Toomas Soome	3 days	1	-0/+2
* 	Fix loader detection of vbefb support on !amd64	Dimitry Andric	=
3 days	1	-2/+2
* 	loader: start kernel in text mode when there is no vbefb vt =
driver	Toomas Soome	3 days	4	-9/+74
* 	loader_lua: consider userboot console as serial	Toomas Soome	=
3 days	1	-1/+4
* 	Add UPDATING entries and bump version	Mark Johnston	2 days	=
2	-1/+8
* 	pam_login_access: Fix negative entry matching logic	Mark =
Johnston	2 days	1	-3/+3
* 	xen-blkback: fix leak of grant maps on ring setup failure	=
Roger Pau Monn=C3=A9	2 days	1	-0/+21

and using: ce9af53d0897a1c~1..ba27dd8be821792
gives:

Commit message (Expand)	Author	Age	Files	Lines
*   	zfs: merge OpenZFS master-9312e0fd1	Martin Matuska	4 days	=
40	-248/+724
|\  =09
| * 	Update vendor/openzfs to master-9312e0fd1vendor/openzfs	Martin =
Matuska	4 days	36	-247/+716
* | 	Fix build after 2c7dc6bae9fd.	Alexander Motin	4 days	1	=
-0/+4
* | 	Refactor CTL datamove KPI.	Alexander Motin	4 days	12	=
-162/+94
* | 	jail: Add pr_state to struct prison	Jamie Gritton	4 days	=
2	-51/+65
* | 	vfs: shrink struct vnode to 448 bytes on LP64	Mateusz Guzik	=
4 days	1	-1/+12
* | 	jail: fix build after the previous commit	Mateusz Guzik	=
4 days	1	-1/+1
* | 	jail: Change the locking around pr_ref and pr_uref	Jamie =
Gritton	4 days	6	-235/+232
* | 	sctp: improve computation of an alternate net	Michael Tuexen	=
5 days	1	-36/+49
* | 	sctp: clear a pointer to a net which will be removed
. . . (all the prior history) . . .

and an empty vs. non-empty status is easier to tell
apart.


=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B105E09A-B2E4-4249-86A5-C64CCDEDEDEF>