-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sat, 5 May 2018 14:12:04 -0700
Matthew Macy schrieb:
> it's in the same place as before but I'll attach just to be clear.
> Gzipped to keep gmail from inserting carriage returns.
> -M
Sorry, missed it.
oh
>
> On Sat, May
it's in the same place as before but I'll attach just to be clear.
Gzipped to keep gmail from inserting carriage returns.
-M
On Sat, May 5, 2018 at 1:54 PM, O. Hartmann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Am Sat, 5 May 2018 13:45:13 -0700
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sat, 5 May 2018 13:45:13 -0700
Matthew Macy schrieb:
> actually can you try the updated patch please, it turns out I need to
> workaround this little shop of horrors:
>
>
> static void
> tcp_usr_detach(struct socket *so)
>
actually can you try the updated patch please, it turns out I need to
workaround this little shop of horrors:
static void
tcp_usr_detach(struct socket *so)
{
struct inpcb *inp;
int rlock = 0;
inp = sotoinpcb(so);
KASSERT(inp != NULL, ("tcp_usr_detach: inp == NULL"));
if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Sat, 5 May 2018 11:21:47 -0700
Matthew Macy schrieb:
> pho@ and sbruno@ tested the patch before commit, I can't readily
> reproduce even though the detach path should be common enough. Please
> tell me if this helps:
>
>
pho@ and sbruno@ tested the patch before commit, I can't readily
reproduce even though the detach path should be common enough. Please
tell me if this helps:
https://people.freebsd.org/~mmacy/inpcb.diff
Thanks.
On Sat, May 5, 2018 at 2:01 AM, O. Hartmann wrote:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Thu, 3 May 2018 22:23:52 +0200
"O. Hartmann" schrieb:
I'm not familiar with kernel debugging, so there are some struggles.
After compiling a debugging kernel on
Version String: FreeBSD 12.0-CURRENT #2 r333269: Sat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Thu, 3 May 2018 12:53:05 -0700
"K. Macy" schrieb:
> Can you give any context on what they're doing? In addition - even on
> a production kernel it's possible to compile in DDB to at least get a
> backtrace. Your report only
Can you give any context on what they're doing? In addition - even on
a production kernel it's possible to compile in DDB to at least get a
backtrace. Your report only gives us enough information to know that
there is _an_ issue. It's difficult to proceed on this alone. I do
have a report from the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am Wed, 2 May 2018 19:36:29 + (UTC)
Stephen Hurd schrieb:
> Author: shurd
> Date: Wed May 2 19:36:29 2018
> New Revision: 333175
> URL: https://svnweb.freebsd.org/changeset/base/333175
>
> Log:
> Separate list
Author: shurd
Date: Wed May 2 19:36:29 2018
New Revision: 333175
URL: https://svnweb.freebsd.org/changeset/base/333175
Log:
Separate list manipulation locking from state change in multicast
Multicast incorrectly calls in to drivers with a mutex held causing drivers
to have to go through
11 matches
Mail list logo