[Bug 241980] panic: I/O to pool appears to be hung on vdev
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241980 --- Comment #27 from Eugene Grosbein --- (In reply to Andriy Gapon from comment #25) I still think "core ZFS" logic of panicing system is wrong. It should just disconnect "non-responding" device from pool having redundancy instead. And continue working with pool in degraded state. This is why we add costly redundancy to pools. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #26 from Michael --- I clarify the nature of the appearance of the fatal trap. When the SR-IOV is off, it boots normally. If you boot the VM with the SR-IOV is on the port "turned on" - a fatal trap. I attach a screenshot and a verbose message log in a text file. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #27 from Michael --- Created attachment 209474 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209474&action=edit screenshot of fatal trap 12 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #28 from Michael --- Created attachment 209475 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209475&action=edit verbose output of boot process, and, fatal trap 12 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #29 from Michael --- (In reply to Konstantin Belousov from comment #24) And this patch did not help. Fatal trap - one to one, as without this patch. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #30 from Hans Petter Selasky --- Can you show the patch you tried as a diff in your source tree? It is very strange neither of the patches work. --HPS -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #31 from Michael --- Only the patch from comment #24 was applied and the GENERIC kernel was compiled. No other changes were made to the source code. The kernel compiles with options: include GENERIC-NODEBUG ident TEST-MASTER options SC_HISTORY_SIZE=8000 nooptions USB_DEBUG options MSGMNB=8192 options MSGMNI=40 options MSGSEG=512 options MSGSSZ=32 options MSGTQL=2048 options ROUTETABLES=122 options IPSEC options TCP_SIGNATURE device enc options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=5000 options IPFIREWALL_NAT options IPDIVERT options DUMMYNET device pf device pflog device pfsync device cpuctl options LIBALIAS options COMPAT_LINUXKPI options NETGRAPH options NETGRAPH_ASYNC options NETGRAPH_BPF options NETGRAPH_BRIDGE options NETGRAPH_CAR options NETGRAPH_CISCO options NETGRAPH_DEFLATE options NETGRAPH_ECHO options NETGRAPH_EIFACE options NETGRAPH_ETHER options NETGRAPH_IFACE options NETGRAPH_IPFW options NETGRAPH_FRAME_RELAY options NETGRAPH_HOLE options NETGRAPH_KSOCKET options NETGRAPH_L2TP options NETGRAPH_LMI options NETGRAPH_MPPC_ENCRYPTION options NETGRAPH_NAT options NETGRAPH_NETFLOW options NETGRAPH_ONE2MANY options NETGRAPH_PIPE options NETGRAPH_PPP options NETGRAPH_PPPOE options NETGRAPH_PPTPGRE options NETGRAPH_RFC1490 options NETGRAPH_PRED1 options NETGRAPH_SOCKET options NETGRAPH_SPLIT options NETGRAPH_TEE options NETGRAPH_TCPMSS options NETGRAPH_TTY options NETGRAPH_VJC options NETGRAPH_VLAN options NETGRAPH_UI -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #32 from Michael --- With a clean system (installed from scratch) and only with the GENERIC kernel git clone git://github.com/freebsd/freebsd.git --progress -v --single-branch -b master /usr/src make cleanworld && make cleandir && make -j12 buildworld && make -j12 buildkernel KERNCONF=GENERIC make installkernel KERNCONF=GENERIC make installworld mergemaster -Ui mlx4en_load="YES" -> /boot/loadr.conf reboot ... fatal trap -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #33 from Michael --- The same fatal trap was noticed when doing checkpoint the virtual machine. Not always - once out of fifty approximately. Checkpoint like this https://www.nakivo.com/blog/need-know-hyper-v-checkpoints/ -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242266] CLang 6.0.1 (Part of the System 12.0) can not Build CLang 8.0.1 from the Port Collection
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242266 Bug ID: 242266 Summary: CLang 6.0.1 (Part of the System 12.0) can not Build CLang 8.0.1 from the Port Collection Product: Base System Version: 12.0-RELEASE Hardware: i386 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: crazymi...@ya.ru Created attachment 209478 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209478&action=edit Requested Files /tmp/AArch64InstPrinter-6bd737.cpp && /tmp/AArch64InstPrinter-6bd737.sh It seems, CLang 6.0.1 (Part of the System 12.0) can not Build CLang 8.0.1 from the Port Collection. The Error happened when Updating Ports in the System. Preparations, Before the Error (Worked Ok): time rm -rf /usr/ports/* /usr/ports/.[!.]* /var/db/portsnap/* /var/db/portsnap/.[!.]* time portsnap fetch extract fetch update time portmaster -B -d --no-confirm `whereis -s -q portmaster` pkg --option AUTOCLEAN=Yes --option ASSUME_ALWAYS_YES=Yes delete "libXp" time portmaster -B -v -d --no-confirm --delete-build-only --delete-packages -y --check-port-dbdir time portmaster -y --check-depends I think, some Ports need LLVM 8.0 for Building, so PortMaster will Build and Install LLVM 8.0, ignoring LLVM 6.0... Next Command generated Error: time portmaster -B -v -d --no-confirm --delete-build-only --delete-packages -a [1396/4930] /usr/bin/c++ -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Target/AArch64/InstPrinter -I/usr/p orts/devel/llvm80/work/llvm-8.0.1.src/lib/Target/AArch64/InstPrinter -I/usr/ports/devel/llvm80/work/llvm-8.0.1.src/lib/Target/AArch64 -Ilib/Target/AArch64 -Iinclude -I/usr/ports/de vel/llvm80/work/llvm-8.0.1.src/include -Ilib/Target/AArch64/InstPrinter/.. -I/usr/ports/devel/llvm80/work/llvm-8.0.1.src/lib/Target/AArch64/InstPrinter/.. -O2 -pipe -march=native - O3 -pipe -march=native -DNDEBUG -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -march=native -O3 -pipe -DNDEBUG -isystem /usr/local/include -fPIC -fvisi bility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers - pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fdiagnostics-color -ffu nction-sections -fdata-sections -O2 -pipe -march=native -O3 -pipe -march=native -DNDEBUG -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -march=native -O3 -pipe -DNDEBUG -isystem /usr/local/include-fno-exceptions -MD -MT lib/Target/AArch64/InstPrinter/CMakeFiles/LLVMAArch64AsmPrinter.dir/AArch64InstPrinter.cpp.o -MF lib/Target/ AArch64/InstPrinter/CMakeFiles/LLVMAArch64AsmPrinter.dir/AArch64InstPrinter.cpp.o.d -o lib/Target/AArch64/InstPrinter/CMakeFiles/LLVMAArch64AsmPrinter.dir/AArch64InstPrinter.cpp.o -c /usr/ports/devel/llvm80/work/llvm-8.0.1.src/lib/Target/AArch64/InstPrinter/AArch64InstPrinter.cpp FAILED: lib/Target/AArch64/InstPrinter/CMakeFiles/LLVMAArch64AsmPrinter.dir/AArch64InstPrinter.cpp.o /usr/bin/c++ -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Target/AArch64/InstPrinter -I/usr/ports/devel/l lvm80/work/llvm-8.0.1.src/lib/Target/AArch64/InstPrinter -I/usr/ports/devel/llvm80/work/llvm-8.0.1.src/lib/Target/AArch64 -Ilib/Target/AArch64 -Iinclude -I/usr/ports/devel/llvm80/w ork/llvm-8.0.1.src/include -Ilib/Target/AArch64/InstPrinter/.. -I/usr/ports/devel/llvm80/work/llvm-8.0.1.src/lib/Target/AArch64/InstPrinter/.. -O2 -pipe -march=native -O3 -pipe -ma rch=native -DNDEBUG -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -march=native -O3 -pipe -DNDEBUG -isystem /usr/local/include -fPIC -fvisibility-inlin es-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wn o-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fdiagnostics-color -ffunction-secti ons -fdata-sections -O2 -pipe -march=native -O3 -pipe -march=native -DNDEBUG -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -march=native -O3 -pipe -DND EBUG -isystem /usr/local/include-fno-exceptions -MD -MT lib/Target/AArch64/InstPrinter/CMakeFiles/LLVMAArch64AsmPrinter.dir/AArch64InstPrinter.cpp.o -MF lib/Target/AArch64/Inst Printer/CMakeFiles/LLVMAArch64AsmPrinter.dir/AArch64InstPrinter.cpp.o.d -o lib/Target/AArch64/InstPrinter/CMakeFiles/LLVMAArch64AsmPrinter.dir/AArch64InstPrinter.cpp.o -c /usr/port s/devel/llvm80/w
[Bug 163830] device smbios: missing documentation, no manpage
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=163830 Gordon Bergling changed: What|Removed |Added CC||gbergl...@gmail.com --- Comment #3 from Gordon Bergling --- A manpage for smbios(4) was submitted in PR240252 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240252 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639
--- Comment #34 from Hans Petter Selasky ---
Hi,
Can you try this patch and get those prints off the DMESG?
Maybe some memory is not zero-initialized ...
--HPS
diff --git a/sys/kern/kern_linker.c b/sys/kern/kern_linker.c
index 6dc21886066..89b575b0ab7 100644
--- a/sys/kern/kern_linker.c
+++ b/sys/kern/kern_linker.c
@@ -1066,6 +1066,9 @@ kern_kldload(struct thread *td, const char *file, int
*fileid)
if ((error = priv_check(td, PRIV_KLD_LOAD)) != 0)
return (error);
+ printf("TD_PROC=%p\n", td->td_proc);
+ printf("P_FD=%p\n", td->td_proc->p_fd);
+
/*
* It is possible that kldloaded module will attach a new ifnet,
* so vnet context must be set when this ocurs.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #35 from Michael --- Created attachment 209482 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209482&action=edit verbose output of boot process with printf TD_PROC & P_FD -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #36 from Konstantin Belousov --- (In reply to Michael from comment #35) Sigh, try this diff --git a/sys/kern/kern_linker.c b/sys/kern/kern_linker.c index 6dc21886066..ed6a8f793ea 100644 --- a/sys/kern/kern_linker.c +++ b/sys/kern/kern_linker.c @@ -1066,6 +1066,9 @@ kern_kldload(struct thread *td, const char *file, int *fileid) if ((error = priv_check(td, PRIV_KLD_LOAD)) != 0) return (error); + if (td->td_proc->p_fd->fd_rdir == NULL) + return (EINVAL); + /* * It is possible that kldloaded module will attach a new ifnet, * so vnet context must be set when this ocurs. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #37 from Michael --- (In reply to Konstantin Belousov from comment #36) Yes! Its work! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #38 from Michael --- Firs, I turn on SR-IOV on port and made screenshot -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #39 from Michael --- Created attachment 209483 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209483&action=edit Turn ON SR-IOV on working VM -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #40 from Michael --- Then, I recompiled the kernel with such changes -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #41 from Michael --- Created attachment 209485 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209485&action=edit make + patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #42 from Michael --- Created attachment 209486 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209486&action=edit verbose output with working patch -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #43 from Konstantin Belousov --- https://reviews.freebsd.org/D22571 should be the committable fix. Please retest with it. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #44 from Michael --- Created attachment 209487 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209487&action=edit verbose output when 'chekpoint' have been made -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242261] nvme0: aborting outstanding i/o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242261 Alexandr Krivulya changed: What|Removed |Added CC||shur...@shurik.kiev.ua --- Comment #1 from Alexandr Krivulya --- This was fixed on CURRENT and MFC-ed to 12-STABLE. See details on bug #211713 You can also try to decrease timeout: sysctl dev.nvme.0.timeout_period=10 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242270] Network stack leaks ifnet references when creating VLAN
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242270
Bug ID: 242270
Summary: Network stack leaks ifnet references when creating
VLAN
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: abo...@pensando.io
When a VLAN is created on a struct ifnet, one extra leaked reference is added
on the ifnet. This reference is never removed and results in a leak of the
ifnet once it is forgotten by the network stack.
Roughly:
* if_clone_create() -> vlan_clone_match() -> vlan_clone_match_ethervid() takes
a ref (1)
* if_clone_createif() -> vlan_clone_create() -> vlan_clone_match_ethervid()
takes a ref (2)
* if_clone_createif() -> vlan_clone_create() -> vlan_config() takes a ref (3)
* if_clone_createif() -> vlan_clone_create() drops a ref (3)
* One ref is dropped when the VLAN is destroyed (2)
* Ref (1) is leaked
The first pass, if_clone_create(), is just to verify that an ifp named "foo0"
is present in the system. When if_clone_createif() goes back for the second
pass, it does the check again and errors out cleanly if the name is not
present. The refcounting was added to this code after it had been in the kernel
for years; prior to the refcounting, it would have been necessary for the
second pass to re-confirm that the port exists.
To me, it seems clear that the first pass was not intended to return with a
reference held. It doesn't return an ifp pointer or anything - just '1' to
indicate that the named interface exists. It would be a much larger redesign to
combine everything into one pass. Instead we should just fix the reference
leak.
(This might only affect foo0.N style VLANs)
This is a fix:
--- a/sys/net/if_vlan.c
+++ b/sys/net/if_vlan.c
@@ -957,10 +957,14 @@ vlan_clone_match_ethervid(const char *name, int *vidp)
static int
vlan_clone_match(struct if_clone *ifc, const char *name)
{
+ struct ifnet *ifp;
const char *cp;
- if (vlan_clone_match_ethervid(name, NULL) != NULL)
+ ifp = vlan_clone_match_ethervid(name, NULL);
+ if (ifp != NULL) {
+ if_rele(ifp);
return (1);
+ }
if (strncmp(vlanname, name, strlen(vlanname)) != 0)
return (0);
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #45 from Michael --- (In reply to Konstantin Belousov from comment #43) Yes. https://reviews.freebsd.org/D22571 also work Made changes in file sys/kern/kern_linker.c and sys/kern/subr_firmware.c OS boot and work ok! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242272] LinuxKPI combines all RCU and SRCU domains together, leading to deadlock
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242272 Bug ID: 242272 Summary: LinuxKPI combines all RCU and SRCU domains together, leading to deadlock Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: abo...@pensando.io In that other OS, all RCU code is in the one domain, and each SRCU user gets its own domain. (More or less.) They are all combined together in FreeBSD since it has only a bare-bones implementation in the KPI. This is a problem because ib_uverbs holds an SRCU read lock when calling into the provider's destroy_cq function. Providers may expect to be able to use RCU primitives when tearing down, but calling synchronize_rcu() or synchronize_srcu() will lead to a deadlock, even on a completely separate SRCU domain. To fix this will require adding real multiple-domain support to the KPI. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242266] CLang 6.0.1 (Part of the System 12.0) can not Build CLang 8.0.1 from the Port Collection
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242266 Brooks Davis changed: What|Removed |Added CC||bro...@freebsd.org --- Comment #1 from Brooks Davis --- Official packages are currently built on 12.0 so I suspect a local issue. Since you indicate that you are running on an i386 system it is likely that the compiler was killed by an out-of-memory or out-of-swap error. Please check dmesg or your logs for errors related to c++. As a workaround you might consider setting the BE_NATIVE option to disable the AArch64 backend. It will also save you a bit of compile time. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #46 from Michael --- https://reviews.freebsd.org/D22571 and GENERIC kernel with options device xz device mlxfw device firmware device mlx4 device mlx4en device mlx5 device mlx5en also work ok! Verbose boot log attached messages.3.txt Verbose dmesg log by made 'checkpoint' VM attached messages.4.txt -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #47 from Michael --- Created attachment 209493 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209493&action=edit verbose boot log with 'patch' and precompiled mlx4 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #48 from Michael --- Created attachment 209494 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209494&action=edit verbose log 'chekpoint' maded -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242225] "fstyp -l" does not report exfat filesystem volume label
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242225 --- Comment #11 from Conrad Meyer --- Created attachment 209495 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209495&action=edit Fixes the bug and adds matching test case Here's a patch that adds the missing functionality, as well as a functional test using the existing exfat test image. It's not clear to me that we can commit it and ship it without drawing the ire of OIN's? Microsoft's? lawyers. So I do not intend to commit it myself. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242225] "fstyp -l" does not report exfat filesystem volume label
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242225 Conrad Meyer changed: What|Removed |Added Attachment #209495|0 |1 is obsolete|| --- Comment #12 from Conrad Meyer --- Created attachment 209496 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209496&action=edit Fixes the bug and adds matching test case, v2 (Obviously I did not actually run the test under ATF the first time around. This fixes the typo's in the atf-sh test case definition.) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242225] "fstyp -l" does not report exfat filesystem volume label
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242225 Conrad Meyer changed: What|Removed |Added Version|11.3-RELEASE|CURRENT -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 232350] periodic: pkg-checksum and pkg-backup interfere with 'overnight' port builds
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232350 --- Comment #26 from Tatsuki Makino --- Should we adjust LOCK_RETRIES and LOCK_WAIT in /usr/local/etc/pkg.conf? LOCK_WAIT = 10 LOCK_RETRIES = 50 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 242132] fix wrong GSS credentials cache expiration date for indefinite tickets
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242132 Rick Macklem changed: What|Removed |Added Assignee|b...@freebsd.org|rmack...@freebsd.org CC||rmack...@freebsd.org Flags||mfc-stable12?, ||mfc-stable11? Status|New |In Progress --- Comment #1 from Rick Macklem --- Take this PR and commit the patch to head. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 241639] Fatal trap 12: page fault ... current process = 0 (vmbusdev) when using mlx4en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241639 --- Comment #49 from Michael --- If someone could help fix the following bugs https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238095 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236042 we get a wonderful super-router for cloud infrastructure -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
