From Newsgroup: muc.lists.freebsd.stable

Colin Percival <cperciva_at_FreeBSD.org> wrote on
Date: Fri, 05 Sep 2025 01:24:00 UTC :

The branch stable/15 has been created by cperciva:

URL: https://cgit.FreeBSD.org/src/commit/?id=6e7cc49f94cf9760125ab1699b6eb9b8311394a5

commit 6e7cc49f94cf9760125ab1699b6eb9b8311394a5
Author: Colin Percival <cperciva@FreeBSD.org>
AuthorDate: 2025-09-04 23:48:10 +0000
Commit: Colin Percival <cperciva@FreeBSD.org>
CommitDate: 2025-09-05 00:06:39 +0000

Make stable/15 a stable branch

* Turn off LLVM assertions
* Turn on production malloc and reproductible builds

Just for my edification for stable/* and release/*.* :
Is there a reason that PTHREADS_ASSERTIONS is
left enabled? (Listed in __DEFAULT_YES_OPTIONS
in share/mk/src.opts.mk .)
Is there a reason that ASSERT_DEBUG
( in share/mk/bsd.opts.mk ) is left enabled
( listed in __DEFAULT_YES_OPTIONS )?

* Set dumpdev="NO" in /etc/defaults/rc.conf
* Remove witness sysctl setting from install images
* Adjust branch to stable/15 in release.conf.sample
* Bump __FreeBSD_version
* Update UPDATING

Adjustments to kernel configurations will come in later commits.

===
Mark Millard
marklmi at yahoo.com
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On 9/4/25 22:02, Mark Millard wrote:

Colin Percival <cperciva_at_FreeBSD.org> wrote on
Date: Fri, 05 Sep 2025 01:24:00 UTC :

* Turn off LLVM assertions
* Turn on production malloc and reproductible builds

Just for my edification for stable/* and release/*.* :

Is there a reason that PTHREADS_ASSERTIONS is
left enabled? (Listed in __DEFAULT_YES_OPTIONS
in share/mk/src.opts.mk .)

That's a good question. I've emailed a few people to ask...

Is there a reason that ASSERT_DEBUG
( in share/mk/bsd.opts.mk ) is left enabled
( listed in __DEFAULT_YES_OPTIONS )?

That's documented as "Compile programs and libraries without the
assert(3) checks" which I'm inclined to say sounds dangerous since
assertions are often misused for security purposes.
--
Colin Percival
FreeBSD Release Engineering Lead & EC2 platform maintainer
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On Sep 5, 2025, at 14:37, Colin Percival <cperciva@tarsnap.com> wrote:

On 9/4/25 23:06, Colin Percival wrote:

On 9/4/25 22:02, Mark Millard wrote:

Colin Percival <cperciva_at_FreeBSD.org> wrote on
Date: Fri, 05 Sep 2025 01:24:00 UTC :

* Turn off LLVM assertions
* Turn on production malloc and reproductible builds

Just for my edification for stable/* and release/*.* :

Is there a reason that PTHREADS_ASSERTIONS is
left enabled? (Listed in __DEFAULT_YES_OPTIONS
in share/mk/src.opts.mk .)

That's a good question. I've emailed a few people to ask...

I've switched PTHREADS_ASSERTIONS to __DEFAULT_NO in stable/15. Thanks
for pointing this out!

Cool.

As for:

QUOTE

Is there a reason that ASSERT_DEBUG
( in share/mk/bsd.opts.mk ) is left enabled
( listed in __DEFAULT_YES_OPTIONS )?

That's documented as "Compile programs and libraries without the
assert(3) checks" which I'm inclined to say sounds dangerous since
assertions are often misused for security purposes.
END QUOTE

assert does not give much control of error handling, if I
remember right. Having them present might give a means of
denial of service via causing the program involved to quit
by failing an assert. No clear win in either orientation
of handling relative to security? (Learning of bugs is a
separate issue.)


===
Mark Millard
marklmi at yahoo.com



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2