[Bug 231045] ipv6 fragment reassembly broken

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231045 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable11+ Keywords|

[Bug 131876] [socket] FD leak by receiving SCM_RIGHTS by recvmsg with small control message buffer

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=131876 Kubilay Kocak changed: What|Removed |Added Version|6.4-RELEASE |11.0-RELEASE Flags|

[Bug 231428] 12.0-ALPHA6 crashes with gif (IPv4 in IPv4) over vtnet

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231428 --- Comment #5 from Matt Macy --- Alright. Let's at least be specific then. Add a: #define INP_INFO_WUNLOCK_ASSERT(ipi) mtx_assert(&(ipi)->ipi_lock, MA_NOTOWNED) Replace INP_INFO_UNLOCK_ASSERT(&V_tcbinfo) on line 803 with INP_I

[Bug 231045] ipv6 fragment reassembly broken

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231045 Xin LI changed: What|Removed |Added CC||delp...@freebsd.org, |

Re: IPv6 fragment reassembly regression following FreeBSD-SA-18:10.ip

2018-09-24 Thread Don Lewis
On 24 Sep, John W. O'Brien wrote: > On 9/23/18 17:50, Don Lewis wrote: >> On 23 Sep, John W. O'Brien wrote: >>> I'd like to check my understanding and then ask a procedural question. >>> >>> FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1]. >>> That changeset, resulting in 11

Re: IPv6 fragment reassembly regression following FreeBSD-SA-18:10.ip

2018-09-24 Thread Andrey V. Elsukov
On 23.09.2018 16:43, John W. O'Brien wrote: > I'd like to check my understanding and then ask a procedural question. > > FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1]. > That changeset, resulting in 11.1R-p13 and 11.2R-p2, included a patch to > the way IPv6 fragment reass

[Bug 230510] iflib/vlan panic: sleeping thread

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230510 Matt Macy changed: What|Removed |Added Status|Open|Closed Resolution|---

Re: IPv6 fragment reassembly regression following FreeBSD-SA-18:10.ip

2018-09-24 Thread John W. O'Brien
On 9/23/18 17:50, Don Lewis wrote: > On 23 Sep, John W. O'Brien wrote: >> I'd like to check my understanding and then ask a procedural question. >> >> FreeBSD-SA-18:10.ip [0], released on 08/14, was resolved by r337828 [1]. >> That changeset, resulting in 11.1R-p13 and 11.2R-p2, included a patch to

[Bug 230655] vlan(4) holds non-sleepable locks around driver ioctls

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230655 Navdeep Parhar changed: What|Removed |Added Resolution|--- |DUPLICATE Status|New

[Bug 230510] iflib/vlan panic: sleeping thread

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230510 Navdeep Parhar changed: What|Removed |Added CC||n...@freebsd.org --- Comment #6 f

Re: setting SSLKEYLOGFILE (for HTTPS decryption) does not work

2018-09-24 Thread Victor Sudakov
Victor Sudakov wrote: > > I have noticed that "env SSLKEYLOGFILE=/var/tmp/keylog.txt firefox" > does not create /var/tmp/keylog.txt on FreeBSD. > > On Windows, this environment variable works as expected (creates a dump > file with SSL keys to be fed to Wireshark for HTTPS decryption). > > What

setting SSLKEYLOGFILE (for HTTPS decryption) does not work

2018-09-24 Thread Victor Sudakov
Dear Colleagues, I have noticed that "env SSLKEYLOGFILE=/var/tmp/keylog.txt firefox" does not create /var/tmp/keylog.txt on FreeBSD. On Windows, this environment variable works as expected (creates a dump file with SSL keys to be fed to Wireshark for HTTPS decryption). What am I doing wrong? I'

[Bug 231659] 12-ALPHA7 r338900 crashes with IPsec on network load

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659 Lev A. Serebryakov changed: What|Removed |Added Summary|12-ALPHA6 r338900 crashes |12-ALPHA7 r338900 crashes

[Bug 231659] 12-ALPHA6 r338900 crashes with IPsec on network load

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231659 Lev A. Serebryakov changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are

I210/igb is limited by flow control and reset fc setting on MTU change (11-STABLE)

2018-09-24 Thread Lev Serebryakov
My 11-STABLE system with igb (I210) can not send more than 710Mbit/s with single TCP stream until I disable flow control (sysctl dev.igb.0.fc=0). After that it shows full-speed and there is no collisions. Other system with I210 doesn't show this behavior. What is worse, after ifconfig igb0

[Bug 231428] 12.0-ALPHA6 crashes with gif (IPv4 in IPv4) over vtnet

2018-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231428 --- Comment #4 from Andrey V. Elsukov --- (In reply to Matthew Macy from comment #3) > I think the assertion is generally useful. Andrey - is there any way to > infer that we're in encap context? In which case we could just set > TI_RLOCKED