[Bug 268162] zfskeys_enable: each successful load of a key is preceded by 'key not found, empty or unreadable'

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268162

Graham Perrin  changed:

   What|Removed |Added

   Keywords||needs-patch
  Component|kern|misc
URL||https://cgit.freebsd.org/sr
   ||c/commit/?id=97aeda2243568b
   ||386d792514996a06daec55eece
   Assignee|b...@freebsd.org|f...@freebsd.org
  Flags||mfc-stable13?
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2624
   ||68
 Status|New |Open

--- Comment #1 from Graham Perrin  ---
Retrospective: 97aeda2243568b386d792514996a06daec55eece 

> zfskeys: Support autoloading of keys stored on ZFS

* paid attention to order.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268162] zfskeys_enable: each successful load of a key is preceded by 'key not found, empty or unreadable'

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268162

Bug ID: 268162
   Summary: zfskeys_enable: each successful load of a key is
preceded by 'key not found, empty or unreadable'
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: grahamper...@freebsd.org
 Attachment #238525 text/plain
 mime type:

Created attachment 238525
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238525=edit
grep -e "key not found" -e "Loading key" /var/log/console.log

Spun off from bug 262468 comment 4, a minor issue. 

The key to the OpenZFS-encrypted dataset is in my home directory. Home on
(GELI-encrypted) ZFS on the internal hard disk of an HP EliteBook 8570p. 

The encrypted dataset is on a mobile hard disk drive on USB.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 266496] bectl list -c origin - Bus error

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266496

Graham Perrin  changed:

   What|Removed |Added

   Keywords||needs-qa
URL||https://www.freebsd.org/cgi
   ||/man.cgi?query=bectl
   ||n=8=FreeBSD
   Assignee|b...@freebsd.org|kev...@freebsd.org
 CC||grahamper...@freebsd.org
 Status|New |Open

--- Comment #1 from Graham Perrin  ---
Not reproducible with 14.0-CURRENT, and (at a glance)
 I see nothing related in
main. 

kevans@ any idea?

(In reply to Slawomir Wojciech Wojtczak from comment #0)

A wild guess, the '.' caught my eye, but does not cause an issue here: 

root@mowa219-gjp4-8570p-freebsd:~ # uname -KU
1400073 1400073
root@mowa219-gjp4-8570p-freebsd:~ # bectl list -c origin
BEActive Mountpoint Space Created
n256570-5c19fabbe34-f -  -  6.49G 2022-07-22 21:06
n257645-160a2f2cdda-b -  -  11.7G 2022-08-29 15:49
n258027-c9baa974717-d -  -  10.2G 2022-09-28 08:46
n258900-aba921bd9e1-a -  -  4.65G 2022-10-29 17:40
n258900-aba921bd9e1-b -  -  118M  2022-11-01 08:59
n259004-2c10be9e06d-a -  -  120M  2022-11-03 03:42
n259004-2c10be9e06d-b -  -  556M  2022-11-03 17:47
n259004-2c10be9e06d-c -  -  503M  2022-11-08 21:54
n259004-2c10be9e06d-d -  -  254M  2022-11-14 01:06
n259004-2c10be9e06d-e -  -  245M  2022-11-15 07:21
n259004-2c10be9e06d-f -  -  307M  2022-11-18 07:14
n259004-2c10be9e06d-g -  -  327M  2022-11-22 00:49
n259004-2c10be9e06d-h -  -  200M  2022-11-25 16:26
n259004-2c10be9e06d-i -  -  64.0M 2022-11-28 22:27
n259461-f4d3aa74908-b NR /  293G  2022-12-02 08:10
n259461-f4d3aa74908-a -  -  64.9M 2022-12-01 06:08
root@mowa219-gjp4-8570p-freebsd:~ # bectl create blah.blah
root@mowa219-gjp4-8570p-freebsd:~ # bectl list -c origin
BEActive Mountpoint Space Created
n256570-5c19fabbe34-f -  -  6.49G 2022-07-22 21:06
n257645-160a2f2cdda-b -  -  11.7G 2022-08-29 15:49
n258027-c9baa974717-d -  -  10.2G 2022-09-28 08:46
n258900-aba921bd9e1-a -  -  4.65G 2022-10-29 17:40
n258900-aba921bd9e1-b -  -  118M  2022-11-01 08:59
n259004-2c10be9e06d-a -  -  120M  2022-11-03 03:42
n259004-2c10be9e06d-b -  -  556M  2022-11-03 17:47
n259004-2c10be9e06d-c -  -  503M  2022-11-08 21:54
n259004-2c10be9e06d-d -  -  254M  2022-11-14 01:06
n259004-2c10be9e06d-e -  -  245M  2022-11-15 07:21
n259004-2c10be9e06d-f -  -  307M  2022-11-18 07:14
n259004-2c10be9e06d-g -  -  327M  2022-11-22 00:49
n259004-2c10be9e06d-h -  -  200M  2022-11-25 16:26
n259004-2c10be9e06d-i -  -  64.0M 2022-11-28 22:27
n259461-f4d3aa74908-b NR /  293G  2022-12-02 08:10
n259461-f4d3aa74908-a -  -  64.9M 2022-12-01 06:08
blah.blah -  -  8K2022-12-05 03:53
root@mowa219-gjp4-8570p-freebsd:~ # bectl destroy blah.blah
root@mowa219-gjp4-8570p-freebsd:~ #

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 263111] Explain *_prepend option in rc.conf(5) man page and in /etc/defaults/rc.conf file

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263111

Graham Perrin  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People
   Keywords||needs-patch, needs-qa
  Component|misc|conf
 CC||grahamper...@freebsd.org
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 263290] freebsd-update(8) should create new /var/db/freebsd-update dir

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263290

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
   Keywords||feature, needs-qa
   Assignee|b...@freebsd.org|grahamper...@freebsd.org

--- Comment #1 from Graham Perrin  ---
For clarity: is an absence of/var/db/freebsd-updatetypically the result
of (for example) someone inadvertently removing the directory, instead of its
contents?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 263576] efibootmgr(8) output: prepend: Boot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263576

Graham Perrin  changed:

   What|Removed |Added

Summary|efibootmgr(8) output|efibootmgr(8) output:
   ||prepend: Boot
 Status|New |Open
   Keywords||feature, needs-qa, uefi

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 259344] HEALTH column misaligned in 'zpool list -v' command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259344

Graham Perrin  changed:

   What|Removed |Added

 Status|New |In Progress
 CC||grahamper...@freebsd.org
   Assignee|b...@freebsd.org|grahamper...@freebsd.org

--- Comment #3 from Graham Perrin  ---
Created attachment 238524
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238524=edit
A non-wrapped view of some of the text from comment 0

Re: comment 0

Output fromzpool list -vLPwas too wide for Bugzilla.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 253248] Instant panic/restart with mdconfig -t malloc and GELI

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253248

Graham Perrin  changed:

   What|Removed |Added

   Keywords||needs-qa
 Status|New |Open
URL||https://www.freebsd.org/cgi
   ||/man.cgi?query=mdconfig
   ||tion=8=FreeBSD
 CC||grahamper...@freebsd.org

--- Comment #3 from Graham Perrin  ---
Reproducible with any/all of the following? 

12.3-RELEASE-p10
13.1-RELEASE-p5
14.0-CURRENT

Thanks

( at a glance, nothing related in
release notes.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 251291] sockstat(1) - use -w option to also make COMMAND column wider

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251291

--- Comment #3 from Graham Perrin  ---
(In reply to Graham Perrin from comment #2)

> Output from the latter could be tidier.

Output from _both_ commands could be tidier (columns in disarray) …

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 251291] sockstat(1) - use -w option to also make COMMAND column wider

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251291

--- Comment #2 from Graham Perrin  ---
Created attachment 238523
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238523=edit
Without and with option -w (wider field size for displaying addresses)

sockstat -lL -4

sockstat -lLw -4

Output from the latter could be tidier.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 251291] sockstat(1) - use -w option to also make COMMAND column wider

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251291

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
   Severity|Affects Only Me |Affects Some People
   Keywords||needs-patch, needs-qa
Version|12.2-RELEASE|CURRENT
 CC||grahamper...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 225395] Make sade(8) (sysadmins disk editor) usable where '/' is not on UFS

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225395

Graham Perrin  changed:

   What|Removed |Added

URL||https://www.freebsd.org/cgi
   ||/man.cgi?query=sade
   ||=8=FreeBSD
   Severity|Affects Only Me |Affects Some People
 CC||grahamper...@freebsd.org
Summary|/usr/sbin/sade is useless   |Make sade(8) (sysadmins
   |when '/' is not on UFS  |disk editor) usable where
   ||'/' is not on UFS
   Keywords||needs-qa

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268157] /etc/rc.d/zpool runs too early, before usb disks available

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268157

Graham Perrin  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|freebsd-...@freebsd.org
 CC||f...@freebsd.org,
   ||grahamper...@freebsd.org
   Keywords||needs-qa
 Status|New |Open
  Component|misc|usb

--- Comment #2 from Graham Perrin  ---
Triage: freebsd-arm@ (assignment) and usb (component), both tentative.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268156] /bin/sh: errors are printed with wrong line numbers in strict mode (set -euo pipefail)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268156

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@freebsd.org
 Status|New |Open
   Severity|Affects Only Me |Affects Some People

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260508] BCM5720 bge0: attaching PHYs failed

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260508

Graham Perrin  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org
 Status|New |Open
   Keywords||needs-qa

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 260508] BCM5720 bge0: attaching PHYs failed

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260508

Graham Perrin  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2681
   ||51

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 262461] bsdinstall: After manual partitioning the disk, installer installs "ZFS on root" directly on the pool not under separate ZFS datasets

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262461

Graham Perrin  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2678
   ||43
 Status|New |Open

--- Comment #4 from Graham Perrin  ---
(In reply to parv from comment #0)

> … no separate ZFS datasets …

A comparable observation in bug 267843 comment 1, step 5. 

Whether there's a common cause, I can not tell. kevans@ maybe?

Triage: increased severity, given the observation.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268157] /etc/rc.d/zpool runs too early, before usb disks available

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268157

--- Comment #1 from Barney Wolff  ---
Adding "sleep 5" to /etc/rc.d/zpool gets around the problem but is surely not
the right fix.

I have this problem on my rpi4. desmg.boot shows zpool aborting just before the
usb disk is detected. So the zpool does not stay imported/mounted across
reboots.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268157] /etc/rc.d/zpool runs too early, before usb disks available

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268157

Bug ID: 268157
   Summary: /etc/rc.d/zpool runs too early, before usb disks
available
   Product: Base System
   Version: 13.1-RELEASE
  Hardware: arm64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: barneywo...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 19683] mount(8) displays incorrect mount point on failed mount

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=19683

Xin LI  changed:

   What|Removed |Added

 CC||delp...@freebsd.org
   Assignee|b...@freebsd.org|mckus...@freebsd.org

--- Comment #6 from Xin LI  ---
I think this can be solved by replacing fs->fs_fsmnt with
mp->mnt_stat.f_mntonname (the code was introduced in
1469eec81e4a8c70124118a552ab06620332a6bd / r8530 in 1995)?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268156] /bin/sh: errors are printed with wrong line numbers in strict mode (set -euo pipefail)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268156

--- Comment #2 from Yuri Victorovich  ---
(In reply to Yuri from comment #1)

Ah, I see.

I think that this error message is confusing. It could say "./x.sh: parameter 1
not set".

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268156] /bin/sh: errors are printed with wrong line numbers in strict mode (set -euo pipefail)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268156

--- Comment #1 from Yuri  ---
That is not the line number though (it does not say "line"), and rather the
variable you tried to reference.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268156] /bin/sh: errors are printed with wrong line numbers in strict mode (set -euo pipefail)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268156

Bug ID: 268156
   Summary: /bin/sh: errors are printed with wrong line numbers in
strict mode (set -euo pipefail)
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: y...@freebsd.org

This script:
> #!/bin/sh
> 
> set -euo pipefail # strict mode
> 
> echo "$1"

fails with:
> ./x.sh: 1: parameter not set

The actual error is in line 5, not line 1.

As a comparison, bash prints a correct line number:
> ./x.sh: line 5: $1: unbound variable

Bash error message is also more relevant.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 18319] dump(8) fails with "cannot reopen disk: interrupted system call"

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=18319

Xin LI  changed:

   What|Removed |Added

 CC||delp...@freebsd.org
 Resolution|--- |Unable to Reproduce
 Status|Open|Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 17993] improving on the default /etc/amd.map

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=17993

Xin LI  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events
 CC||delp...@freebsd.org

--- Comment #3 from Xin LI  ---
amd(8) is retired in r358821.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 17108] [nfs] SecureRPC not supported in mount_nfs command

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=17108

Xin LI  changed:

   What|Removed |Added

 CC||delp...@freebsd.org
   Assignee|b...@freebsd.org|rmack...@freebsd.org

--- Comment #4 from Xin LI  ---
Over to maintainer (we should probably close this as WONTFIX as SecureRPC is
using obsolete encryption methods, etc.).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 16765] Add support for mark/space parity

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=16765

Xin LI  changed:

   What|Removed |Added

 Depends on|237576  |


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237576
[Bug 237576] UART NS8250 parity and frame errors detection doesn't work
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 237576] UART NS8250 parity and frame errors detection doesn't work

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237576

Xin LI  changed:

   What|Removed |Added

 CC||delp...@freebsd.org
 Blocks|16765   |


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=16765
[Bug 16765] Add support for mark/space parity
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 237576] UART NS8250 parity and frame errors detection doesn't work

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237576

Xin LI  changed:

   What|Removed |Added

 CC||docon...@onan.gsoft.com.au

--- Comment #2 from Xin LI  ---
*** Bug 16765 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 16765] Add support for mark/space parity

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=16765

Xin LI  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||delp...@freebsd.org
 Resolution|--- |DUPLICATE

--- Comment #6 from Xin LI  ---


*** This bug has been marked as a duplicate of bug 237576 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 13108] authunix_create_default includes egid twice

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=13108

Xin LI  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||bro...@freebsd.org,
   ||delp...@freebsd.org
 Status|Open|Closed

--- Comment #5 from Xin LI  ---
This appears to be fixed by r194494.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 2090] [patch] [nis] clients may bind to FreeBSD ypserv refusing to serve them

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2090

Xin LI  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||delp...@freebsd.org
 Resolution|--- |Overcome By Events

--- Comment #6 from Xin LI  ---
portmap(8) was replaced by rpcbind(8) in 2001.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Problem reports for b...@freebsd.org that need special attention

[bugzilla-noreply]

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |197876 | [devfs] an error in devfs leads to data loss and  
New |198797 | [PATCH] Added an option to install BSDstats to bs 
New |202362 | ntp: restore refclocks selection (10.2-RELEASE re 
New |202740 | vi/ex string substitution problem when there is m 
New |204097 | witness_initialize() does not perform bound check 
New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi 
New |209213 | UEFI Loader shows only black screen with Nvidia G 
New |210804 | installerconfig - using ZFS create in custom scri 
New |223470 | freebsd-update: Cannot identify running kernel (/ 
New |230620 | "install -d" issue
New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( 
New |252123 | fetch(3): Fix wrong usage of proxy when request i 
Open|177821 | sysctl: Some security.jail nodes are funky, dupli 
Open|182466 | [headers] [patch] make  self-contained  
Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf 
Open|192573 | Add ps(1) option: Print process start time in sec 
Open|194925 | [pf] [ifconfig] interface group keywords do not w 
Open|197921 | scheduler: Allow non-migratable threads to bind t 
Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4)  
Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C 
Open|207940 | stand/efi/boot1: Add boot partition selection 
Open|212608 | sockstat(1) and lsof(8) can not identity the owne 
Open|220246 | syslogd does not send RFC3164-conformant messages 
Open|221305 | Mouse cursor loss when moving cursor while loadin 
Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL 
Open|221854 | makefs: Reject UFS labels that are too long to fi 
Open|226893 | freebsd-update: Support patchlevel argument for f 
Open|231810 | [build] release always fails with "mkimg: partiti 
Open|233578 | Unprivileged local user can prevent other users l 
Open|233988 | freebsd-update: Improve progress output on termin 
Open|236718 | system panics with message: vm_fault_hold: fault  
Open|237287 | moused(8) ignores button release events in virtua 
Open|237924 | Possible infinite loop in function empty_aux_buff 
Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana 
Open|238486 | Possible buffer overflow bug in sc_allocate_keybo 
Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 
Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c 
Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea 
Open|241697 | i915kms: Kernel panic loading module on custom ke 
Open|247132 | Fix build error: use of undeclared identifier 'cp 
Open|248352 | mfi(4): Remove RAID map sync functionality
Open|257149 | CFLAGS not passed to whole build  
New |260138 | TPM2 Support in bootloader / kernel in order to r 
New |261306 | Geli rc.d script does not support insertion of US 
New |262957 | mpr(4), mps(4): change formally to formerly   
New |267537 | contrib/nvi: Fix core dump when tags file pattern 
Open|179832 | manual page of mac_from_text suggests incorrect f 

47 problems total for which you should take action.

[Bug 260508] BCM5720 bge0: attaching PHYs failed

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260508

grandsuperu...@gmail.com changed:

   What|Removed |Added

 CC||grandsuperu...@gmail.com

--- Comment #1 from grandsuperu...@gmail.com ---
Similar Bug #268151 opened.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268100] 13.1's loader.efi is not able to find a ZFS pool if it was checkpointed on 12.3

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268100

--- Comment #2 from m...@netfence.it ---
(In reply to Warner Losh from comment #1)

First off, there are no "characteristics of the ZFS snapshot": we are talking
about "zpool checkpoint", not "zfs snap".

I have no idea on why loader.efi can't boot from a checkpointed ZFS pool: 
I only saw the message above ("can not read checkpoint data").

I don't have the original problematic pool anymore: it was a production server
and I needed to boot it ASAP, so I just issued "zpool checkpoint -d" (that is,
as soon as I relized what the problem was).
I guess, in order to recreate the situation, procedure would be: install 12.3
UEFI+ZFS, checkpoint, upgrade to 13.1 (maybe upgrading boot loader is enough).
The only thing I could add is it was a zraid5 pool (3 disks); not sure it
matters.

Importance is "less than bulk" to me: it would have saved me three hours of
spreading panic if I had known; now I'll simply check if a checkpoint exists
before upgrading (or, if I forget, boot from an USB key and remove it later).
My only goal was to let other people know, so maybe they won't be hit so hard
by this.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268100] 13.1's loader.efi is not able to find a ZFS pool if it was checkpointed on 12.3

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268100

Warner Losh  changed:

   What|Removed |Added

 CC||i...@freebsd.org

--- Comment #1 from Warner Losh  ---
I need more specific details on how to recreate this. Why can't loader.efi see
it? What are the characteristics of the ZFS snapshot that gives the loader
grief?

Does this persist in a zfs send -> zfs receieve? If so can I get that dataset?

How important is this to you working?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 234130] Shutdown due to overheating after resuming from S3 on coreboot

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234130

y...@noema.org changed:

   What|Removed |Added

 CC||y...@noema.org

--- Comment #5 from y...@noema.org ---
Increase hw.acpi.thermal.polling_rate to
something like 20 should `fix' the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268149] kadmind handle_mit() rpc/gss bugs

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268149

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
 CC||n...@freebsd.org
   Keywords||crash, needs-qa

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268138] graphics/drm-510-kmod: i915kms: panic following screen glitches (page fault with linux_enable="YES")

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268138

Graham Perrin  changed:

   What|Removed |Added

  Component|misc|Individual Port(s)
Product|Base System |Ports & Packages
   Assignee|b...@freebsd.org|x...@freebsd.org
URL|https://www.freebsd.org/cgi |https://www.freshports.org/
   |/man.cgi?query=rc.conf |graphics/drm-510-kmod/
   |ion=5=FreeBSD   |
Version|13.1-RELEASE|Latest
Summary|Panic: page fault with  |graphics/drm-510-kmod:
   |linux_enabled="YES" |i915kms: panic following
   ||screen glitches (page fault
   ||with linux_enable="YES")

--- Comment #4 from Graham Perrin  ---
(In reply to Ruby from comment #3)

Thanks. Is your X220 amongst those that have been probed here? 



(In reply to Ruby from comment #0)

> 13.1-RELEASE

Are panics reproducible if you update the system? 

(The routine at

is not only for security advisories; it's also for errata notices.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268100] 13.1's loader.efi is not able to find a ZFS pool if it was checkpointed on 12.3

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268100

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
   Keywords||loader, needs-qa
  Component|misc|kern
 CC||d...@freebsd.org,
   ||f...@freebsd.org,
   ||grahamper...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268141] Add support for Macmini 6,1 and 6,2 (late 2012) models

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268141

Graham Perrin  changed:

   What|Removed |Added

   Keywords||needs-qa
 CC||grahamper...@freebsd.org
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268093] killall(1) allow sending signals to pts(4)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268093

Graham Perrin  changed:

   What|Removed |Added

URL||https://cgit.freebsd.org/sr
   ||c/commit/?id=e442917ee41986
   ||c416afea1d152ad03c5daeeac4
   Assignee|b...@freebsd.org|k...@freebsd.org
 Status|New |In Progress
  Flags||mfc-stable13?,
   ||mfc-stable12?
 CC||grahamper...@freebsd.org
Summary|[PATCH] killall(1) allow|killall(1) allow sending
   |sending signals to pts(4)   |signals to pts(4)

--- Comment #4 from Graham Perrin  ---
Thanks. 

Triage: [patch] is amongst the summary line tags that are deprecated. 

MFC to both stable/13 and stable/12, or just 13?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268138] Panic: page fault with linux_enabled="YES"

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268138

--- Comment #3 from Ruby  ---
(In reply to Graham Perrin from comment #1)
Sorry, it was a typo
(In reply to Graham Perrin from comment #2)
first i enabled

linux_enable="YES"

then ran

# service linux start

and installed linux_base-c7

# doas pkg install linux_base-c7

after that, i tried to run my linux application, but it failed for some reason
so i put it aside, but after a while i started getting kernel panics and the
system slowing down.

After every system startup i just logged in, started my xorg server, started my
browser and noticed that the screen was glitching for some reason. and after it
started to do it more and more it panicked.

I have a Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz with 8 gigabytes of ram, and
its a x220 laptop.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268116] ZFS: panic (VERIFY0(0 == nvlist_lookup_uint64(nvl, name, )) failed (0 == 22)) – reboot after readding ZIL device

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268116

Graham Perrin  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|f...@freebsd.org
 CC||grahamper...@freebsd.org
Summary|reboot after readding ZIL   |ZFS: panic (VERIFY0(0 ==
   |device to ZFS   |nvlist_lookup_uint64(nvl,
   ||name, )) failed (0 ==
   ||22)) – reboot after
   ||readding ZIL device
 Status|New |Open
   Keywords||crash, needs-qa

--- Comment #1 from Graham Perrin  ---
Can you provide more information about the crash? 

Maybe, the most recent core.txt.⋯ file from /var/crash (if there's no such
file, please see savecore(8) and related pages). 



Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268149] kadmind handle_mit() rpc/gss bugs

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268149

Bug ID: 268149
   Summary: kadmind handle_mit() rpc/gss bugs
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: r...@lcs.mit.edu
 Attachment #238511 text/plain
 mime type:

Created attachment 238511
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=238511=edit
tickle bugs in kadmind's RPC/GSS interface by sending RPCs in the clear

The heimdal kadmind has code to receive requests via ONC RPC protected
by GSS encryption and signatures; this is handle_mit() etc in
kadmind/rpc.c.

One problem is that kadmind reads RPC arguments in the clear direct
from the TCP connection, with no encryption or signature (and not
preceded by a length). This means that an eavesdropper could read
or modify RPC arguments (including, I believe, the passwords in
create requests).

That is, when receiving an RPC on a connection that's already been set
up and had initial authentication done, process_stream(...,sp) in
kadmind/rpc.c does this:

  read an RPC length from sp (which is just the socket, no crypto yet);
  read_data(sp, msg, len); // copy bytes from sp socket to msg buffer
  parse the RPC header, including cred and verf, out of msg;
  case RPC_DATA:
gss_unwrap(...  ...) which I believe decrypts, and checks the
signature
(*procs[chdr.proc].func)(server_handle, sp, dreply);

Note that the 2nd argument to procs[].func is sp, not gout or sp1.
That is, the RPC handler function is going to read its arguments
in clear-text from the underlying socket, not from a data buffer
that is the result of decryption and signature check.

Separately, after the RPC handler has returned, process_stream() 
frees sp but then uses it to send the reply:

krb5_storage_free(sp);
... much later;
CHECK(krb5_store_uint32(sp, data.length | LAST_FRAGMENT));
sret = krb5_storage_write(sp, data.data, data.length);

This potentially results in reading and writing and calling through
garbage pointers.

Separately, there are a couple of calls to ret_string_xdr() and
ret_principal_xdr() that assume that if these fuctions return zero
(success), then they allocated a string. That's not the case: if the
client specified a zero-length string, these functions set the string
pointer to NULL.

I've attached a demo. Due to some error in my setup, the host name
must be set to "admin" in order for this to work; otherwise the gss rpc
library changes "kadmin/admin" to "kadmind\\/admin", which kdc doesn't
recognize. valgrind or a debugging malloc is required to see the
use-after-free. kinit is required.

# cc kadmind27a.c -lrpcsec_gss
# hostname admin
# kinit
# valgrind /usr/libexec/kadmind --debug &
# ./a.out

If the user has no kadmind permissions, I get the use-after-free bug:

#0  0x0f24b3546b31 in krb5_store_int (sp=0xf24bb6d6180, 
value=, len=4)
at /usr/src/crypto/heimdal/lib/krb5/store.c:328
#1  krb5_store_int32 (sp=0xf24bb6d6180, value=)
at /usr/src/crypto/heimdal/lib/krb5/store.c:356
#2  krb5_store_uint32 (sp=sp@entry=0xf24bb6d6180, value=)
at /usr/src/crypto/heimdal/lib/krb5/store.c:375
#3  0x0f1c8fc8d07d in process_stream (contextp=0xf24bb6d7000, 
buf=0xf24b0753974 "$\017", ilen=0, sp=0xf24bb6d6180)
at /usr/src/crypto/heimdal/kadmin/rpc.c:1087
#4  handle_mit (contextp=contextp@entry=0xf24bb6d7000, 
buf=buf@entry=0xf24b0753970, len=len@entry=4, sock=)
at /usr/src/crypto/heimdal/kadmin/rpc.c:1107
#5  0x0f1c8fc8e46a in kadmind_loop (contextp=0xf24bb6d7000, 
keytab=0xf24bb6eb000, sock=-1)
at /usr/src/crypto/heimdal/kadmin/server.c:591
#6  0x0f1c8fc8fae9 in main (argc=, argv=)
at /usr/src/crypto/heimdal/kadmin/kadmind.c:202

If the user has kadmind permissions, kadmind crashes when trying
to use a NULL principal name:

#0  _hdb_fetch_kvno (context=0x6972dc59000, db=0x6972dc74000, principal=0x0, 
flags=93, kvno=0, entry=0x6971fd5d880)
at /usr/src/crypto/heimdal/lib/hdb/common.c:110
#1  0x069721cadb81 in kadm5_s_delete_principal (
server_handle=0x6972dc5a040, princ=0x0)
at /usr/src/crypto/heimdal/lib/kadm5/delete_s.c:51
#2  0x068efeee0140 in proc_delete_principal (contextp=0x6972dc5a040, 
in=, out=0x6972dc58200)
at /usr/src/crypto/heimdal/kadmin/rpc.c:597
#3  0x068efeee1d15 in process_stream (contextp=0x6972dc59000, 
buf=0x6971fd5dd14 "\227\006", ilen=0, sp=0x6972dc58180)
at /usr/src/crypto/heimdal/kadmin/rpc.c:926
#4  handle_mit (contextp=contextp@entry=0x6972dc59000, 
buf=buf@entry=0x6971fd5dd10, len=len@entry=4, sock=)
at /usr/src/crypto/heimdal/kadmin/rpc.c:1107
#5  0x068efeee346a in kadmind_loop (contextp=0x6972dc59000, 
keytab=0x6972dc6d000, sock=93)
at 

[Bug 268138] Panic: page fault with linux_enabled="YES"

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268138

Graham Perrin  changed:

   What|Removed |Added

   Keywords||needs-qa

--- Comment #2 from Graham Perrin  ---
Can you tell more about the steps that led to the panic?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268138] Panic: page fault with linux_enabled="YES"

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268138

Graham Perrin  changed:

   What|Removed |Added

   Keywords||crash
Product|Ports & Packages|Base System
  Component|Individual Port(s)  |misc
 CC||grahamper...@freebsd.org
Version|Latest  |13.1-RELEASE
 Status|New |Open
   Assignee|ports-b...@freebsd.org  |b...@freebsd.org
URL||https://www.freebsd.org/cgi
   ||/man.cgi?query=rc.conf
   ||ion=5=FreeBSD

--- Comment #1 from Graham Perrin  ---
> linux_enabled

Was that a typo (the d) here in Bugzilla, or did you use that in your rc.conf
file? 

It should be: 

linux_enable

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 210432] vt(4) does not support boot time splash screen

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210432

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@freebsd.org
 Status|Open|In Progress

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 210432] vt(4) does not support boot time splash screen

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210432

Graham Perrin  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2680
   ||95

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 267871] /usr/bin/rs compile fails after udate to c++

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267871

de...@stasyan.com changed:

   What|Removed |Added

 CC||de...@stasyan.com

--- Comment #5 from de...@stasyan.com ---
I saw the same bug yesterday.

1) Get the fresh tree to the new dir /usr/src:
git clone --branch main https://git.FreeBSD.org/src.git /usr/src
2) make buildworld 
3) stop at 
No such file or directory: '/usr/src/usr.bin/rs/rs.c
4) /usr/src/usr.bin/rs # make clean
===> tests (clean)
rm -f rs_test rs_test.tmp Kyuafile Kyuafile.tmp
rm -rf checkdir
rm -f rs.o rs.bc rs.ll rs.full.bc rs.full.ll rs rs.bc rs.ll rs.full rs.debug
rs.o rs.bc rs.ll rs.1.gz rs.1.cat.gz
5) make -DNO_CLEAN buildworld
and world built successfully.

So it's no relation with old builds, because it was first build in fresh
/usr/src.

-- 
You are receiving this mail because:
You are the assignee for the bug.