Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Jul 2025 08:54:49 -0400
From:      Mark Johnston <markj@freebsd.org>
To:        Konstantin Belousov <kib@freebsd.org>
Cc:        src-committers@freebsd.org, dev-commits-src-all@freebsd.org, dev-commits-src-main@freebsd.org
Subject:   Re: git: 01a679715f68 - main - err(3): print extended error if available
Message-ID:  <aG0VGUnLgBbHAJmZ@nuc>
In-Reply-To: <202507071928.567JSk8Y012639@gitrepo.freebsd.org>
References:  <202507071928.567JSk8Y012639@gitrepo.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 07, 2025 at 07:28:46PM +0000, Konstantin Belousov wrote:
> The branch main has been updated by kib:
> 
> URL: https://cgit.FreeBSD.org/src/commit/?id=01a679715f68d5e32efecafc1f158eecec3f781b
> 
> commit 01a679715f68d5e32efecafc1f158eecec3f781b
> Author:     Konstantin Belousov <kib@FreeBSD.org>
> AuthorDate: 2025-06-16 21:26:22 +0000
> Commit:     Konstantin Belousov <kib@FreeBSD.org>
> CommitDate: 2025-07-07 18:44:22 +0000
> 
>     err(3): print extended error if available
>     
>     Reviewed by:    asomers, brooks
>     Sponsored by:   The FreeBSD Foundation
>     Differential revision:  https://reviews.freebsd.org/D51141

This seems to cause extended errors to be printed unconditionally:

root@freebsd:~ # truncate -r foo bar
truncate: foo: No such file or directory (extended error No error)

A number of tests fail due to this.  Moreover, it doesn't seem useful to
print a non-existent extended error.  Can the extended error be
suppressed in the "no error" case?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aG0VGUnLgBbHAJmZ>