Re: mld_mtx lock order reversal

Michael Tuexen wrote: Dear all, when doing a ifconfig gif0 down ifconfig gif0 -tunnel ifconfig gif0 destroy I got a the following message on the last command. Is this a false positive? See comments in mld6.c. Some LOR warnings are unavoidable at the moment because of INET6 locking; the worst

Richiesta

SOFTWARE PER L' EMAIL-MARKETING Software che estrapola dati dalle Pagine Gialle e Bianche. Software per creare le email info@ da ricerche on line su motori Software Gestionale per inviare newsletter 800 server smtp per inviare le tue newsletter (10.000 per ora) ps: il servizio smtp non è so

mld_mtx lock order reversal

Dear all, when doing a ifconfig gif0 down ifconfig gif0 -tunnel ifconfig gif0 destroy I got a the following message on the last command. Is this a false positive? Best regards Michael --- syscall (304, FreeBSD ELF64, kldload), rip = 0x8006923ac, rsp = 0x7fffed38, rbp = 0 --- lock order r

Re: R: IPv6 and ipfw

Raffaele De Lorenzo wrote: Hi all, I attached a patch that solve this problem. I will send a PR as soon as possible. Instructions: Patch the follow files: /usr/src/sbin/ipfw/ipfw2.c (patch is ipfw2.c.diff) /usr/src/sbin/ipfw/ipfw2.h (patch is ipfw2.h.diff) /usr/src/sbin/ipfw/ipv6.c (patch is

TCP initial window size

Can anybody explain me about initial TCP window sent to the client (in syn/ack packet), please. Is it unmanageable and always set to net.inet.tcp.recvspace? (Due to use of syncache and syncache code is (tcp_syncache.c): /* Initial receive window: clip sbspace to [0 .. TCP_MAXWIN] */