[Bug 261566] Padding of DLT_PFLOG packets should be done differently

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261566 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=c6745a0cc40e77ed3b783a0a8050b42bdf682e57 commit c6745a0cc40e77ed3b783a0a8050b42bdf682e57 Author:

[Bug 261566] Padding of DLT_PFLOG packets should be done differently

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261566 Kristof Provost changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 261566] Padding of DLT_PFLOG packets should be done differently

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261566 --- Comment #6 from commit-h...@freebsd.org --- A commit in branch stable/12 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=275f412b070f0d23b028f8bde85182a1f6d0fe7c commit 275f412b070f0d23b028f8bde85182a1f6d0fe7c Author:

[Bug 261453] Fix a possible Null pointer dereference in ocs_hw_get_profile_list_cb()

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261453 --- Comment #2 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=7bf31432fd03e2a5a815d1cc81de9a7b1ea3d3ca commit 7bf31432fd03e2a5a815d1cc81de9a7b1ea3d3ca Author:

[Bug 261453] Fix a possible Null pointer dereference in ocs_hw_get_profile_list_cb()

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261453 Ram Kishore Vegesna changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 259553] add host 127.0.0.1: gateway lo0 fib 0: route already in table

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259553 Nick Hibma changed: What|Removed |Added CC||melif...@freebsd.org,

[Bug 261827] ifconfig name should not print out the newly set name

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261827 Bug ID: 261827 Summary: ifconfig name should not print out the newly set name Product: Base System Version: Unspecified Hardware: Any URL: https://cgit.freebsd.org/src/com

[Bug 261828] ifconfig name should not print out the newly set name

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 Bug ID: 261828 Summary: ifconfig name should not print out the newly set name Product: Base System Version: Unspecified Hardware: Any URL: https://cgit.freebsd.org/src/com

[Bug 261803] System hang under load (possibly only when running bhyve)

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261803 --- Comment #1 from mmata...@gmail.com --- I was doing a bug compilation without bhyve running today and my system briefly locked up but came back after 10 or so seconds. -- You are receiving this mail because: You are the assignee for the

[Bug 261828] ifconfig name should not print out the newly set name

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 --- Comment #1 from Kristof Provost --- What's preventing your startup script from doing >/dev/null? I note that this behaviour has been in place for 6 years, so I'm very reluctant to change that at this point. -- You are receiving this

[Bug 261828] ifconfig name should not print out the newly set name

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 --- Comment #2 from Nick Hibma --- ... I missed that printifname is being referenced in ifclone.c as well, where the actual problem that the atexit() fixes is caused. So perhaps only printifname=1 in setifname is to be removed from setifnam

[Bug 261828] ifconfig name should not print out the newly set name

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 --- Comment #3 from Nick Hibma --- (In reply to Kristof Provost from comment #1) It's /etc/rc that is producing this output. FreeBSD defaults to no news is good news. Unlike Linux that is much more chatty. There is no use for the printing

[Bug 261828] ifconfig name should not print out the newly set name

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 --- Comment #4 from Kristof Provost --- *** Bug 261827 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

[Bug 261827] ifconfig name should not print out the newly set name

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261827 Kristof Provost changed: What|Removed |Added Resolution|--- |DUPLICATE Status|New

[Bug 261728] If sh became a usable interactive shell, then why can't it tab-autocomplete file.(mine).1.txt and file.(mine).2.txt?

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261728 Daniel Tameling changed: What|Removed |Added Attachment #231647|0 |1 is obsolete|

[Bug 261291] ESX NFS4.1 client hangs, server never responds to EXCHANGE_ID/CREATE_SESSION

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291 --- Comment #17 from Alan Somers --- 1) After nfsrevoke, the server does reply NFS4ERR_ADMIN_REVOKED to the next CREATE_SESSION. Then the client tries a new EXCHANGE_ID, and this time the server replies with a different client_id. The nex

[Bug 261291] ESX NFS4.1 client hangs, server never responds to EXCHANGE_ID/CREATE_SESSION

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261291 --- Comment #18 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=17a56f3fabdfacb62f6d8858643cdb1861c8c1b5 commit 17a56f3fabdfacb62f6d8858643cdb1861c8c1b5 Author:

[Bug 261553] vt newcons: double click does not mark whole word if word starts at beginning of line

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261553 Ed Maste changed: What|Removed |Added Status|New |Open -- You are receiving this mail be

[Bug 261850] Ext2 FileSystem: There is a bug in disk data block allocation

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261850 Bug ID: 261850 Summary: Ext2 FileSystem: There is a bug in disk data block allocation Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any

[Bug 261850] fs/ext2fs: Fix bug in disk data block allocation

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261850 Kubilay Kocak changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org See Als

[Bug 261707] panic: vm_page_free_prep: freeing mapped page 0xfffffe0006f80170 on 14-Current(master-n252892-e30fceb89b7)

2022-02-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261707 Aleksander Slomka changed: What|Removed |Added CC||a...@alexslomka.xyz --- Commen