> On Oct 17, 2017, at 7:52 AM, Michael Tuexen
> wrote:
>
>> On 17. Oct 2017, at 03:32, Lewis Donzis wrote:
>>
>> Would appreciate some guidance on this. It seems like a reasonably serious
>> regression, so I’m surprised it hasn’t already been fixed.
> I just MFCed the fix to stable/11:
>
>
> On 17. Oct 2017, at 03:32, Lewis Donzis wrote:
>
> Would appreciate some guidance on this. It seems like a reasonably serious
> regression, so I’m surprised it hasn’t already been fixed.
I just MFCed the fix to stable/11:
https://svnweb.freebsd.org/base?view=revision&revision=324686
Does th
> On 17. Oct 2017, at 03:32, Lewis Donzis wrote:
>
> Would appreciate some guidance on this. It seems like a reasonably serious
> regression, so I’m surprised it hasn’t already been fixed.
>
> Since all of our code binds a particular library, we were able to work around
> it by overriding the
Would appreciate some guidance on this. It seems like a reasonably serious
regression, so I’m surprised it hasn’t already been fixed.
Since all of our code binds a particular library, we were able to work around
it by overriding the weak referenced socket() with our own version that creates
th
Hello.
This particular bug is a real problem in our embedded system, and we’re trying
to decide whether to go back to 11.0 or wait for a patch for 11.1.
We downloaded just the one file containing the fix, but it wouldn’t compile, so
we downloaded -CURRENT and verified that it works fine. But i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221385
Michael Tuexen changed:
What|Removed |Added
Assignee|freebsd-net@FreeBSD.org |tue...@freebsd.org
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221385
Michael Tuexen changed:
What|Removed |Added
CC||tue...@freebsd.org
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221385
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
