Searched hist:dc56e98f0d95e809a1044d38f86dd9e734857fe0 (Results 1 – 4 of 4) sorted by relevance
| /freebsd/sys/net/ |
| H A D | if_llatbl.h | diff dc56e98f0d95e809a1044d38f86dd9e734857fe0 Tue Aug 25 11:52:38 CEST 2009 Robert Watson <rwatson@FreeBSD.org> Use locks specific to the lltable code, rather than borrow the ifnet
list/index locks, to protect link layer address tables. This avoids
lock order issues during interface teardown, but maintains the bug that
sysctl copy routines may be called while a non-sleepable lock is held.
Reviewed by: bz, kmacy
MFC after: 3 days
diff dc56e98f0d95e809a1044d38f86dd9e734857fe0 Tue Aug 25 11:52:38 CEST 2009 Robert Watson <rwatson@FreeBSD.org> Use locks specific to the lltable code, rather than borrow the ifnet
list/index locks, to protect link layer address tables. This avoids
lock order issues during interface teardown, but maintains the bug that
sysctl copy routines may be called while a non-sleepable lock is held.
Reviewed by: bz, kmacy
MFC after: 3 days
|
| H A D | if_llatbl.c | diff dc56e98f0d95e809a1044d38f86dd9e734857fe0 Tue Aug 25 11:52:38 CEST 2009 Robert Watson <rwatson@FreeBSD.org> Use locks specific to the lltable code, rather than borrow the ifnet
list/index locks, to protect link layer address tables. This avoids
lock order issues during interface teardown, but maintains the bug that
sysctl copy routines may be called while a non-sleepable lock is held.
Reviewed by: bz, kmacy
MFC after: 3 days
diff dc56e98f0d95e809a1044d38f86dd9e734857fe0 Tue Aug 25 11:52:38 CEST 2009 Robert Watson <rwatson@FreeBSD.org> Use locks specific to the lltable code, rather than borrow the ifnet
list/index locks, to protect link layer address tables. This avoids
lock order issues during interface teardown, but maintains the bug that
sysctl copy routines may be called while a non-sleepable lock is held.
Reviewed by: bz, kmacy
MFC after: 3 days
|
| /freebsd/sys/netinet6/ |
| H A D | in6.c | diff dc56e98f0d95e809a1044d38f86dd9e734857fe0 Tue Aug 25 11:52:38 CEST 2009 Robert Watson <rwatson@FreeBSD.org> Use locks specific to the lltable code, rather than borrow the ifnet
list/index locks, to protect link layer address tables. This avoids
lock order issues during interface teardown, but maintains the bug that
sysctl copy routines may be called while a non-sleepable lock is held.
Reviewed by: bz, kmacy
MFC after: 3 days
diff dc56e98f0d95e809a1044d38f86dd9e734857fe0 Tue Aug 25 11:52:38 CEST 2009 Robert Watson <rwatson@FreeBSD.org> Use locks specific to the lltable code, rather than borrow the ifnet
list/index locks, to protect link layer address tables. This avoids
lock order issues during interface teardown, but maintains the bug that
sysctl copy routines may be called while a non-sleepable lock is held.
Reviewed by: bz, kmacy
MFC after: 3 days
|
| /freebsd/sys/netinet/ |
| H A D | in.c | diff dc56e98f0d95e809a1044d38f86dd9e734857fe0 Tue Aug 25 11:52:38 CEST 2009 Robert Watson <rwatson@FreeBSD.org> Use locks specific to the lltable code, rather than borrow the ifnet
list/index locks, to protect link layer address tables. This avoids
lock order issues during interface teardown, but maintains the bug that
sysctl copy routines may be called while a non-sleepable lock is held.
Reviewed by: bz, kmacy
MFC after: 3 days
diff dc56e98f0d95e809a1044d38f86dd9e734857fe0 Tue Aug 25 11:52:38 CEST 2009 Robert Watson <rwatson@FreeBSD.org> Use locks specific to the lltable code, rather than borrow the ifnet
list/index locks, to protect link layer address tables. This avoids
lock order issues during interface teardown, but maintains the bug that
sysctl copy routines may be called while a non-sleepable lock is held.
Reviewed by: bz, kmacy
MFC after: 3 days
|