Searched hist:"6 e6b5143" (Results 1 – 2 of 2) sorted by relevance
/freebsd/sys/netinet/ |
H A D | ip_reass.c | 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153
|
/freebsd/sys/netinet6/ |
H A D | frag6.c | 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153 6e6b5143 Fri Oct 25 18:54:06 GMT 2019 Bjoern A. Zeeb <bz@FreeBSD.org> Properly set VNET when nuking recvif from fragment queues.
In theory the eventhandler invoke should be in the same VNET as the the current interface. We however cannot guarantee that for all cases in the future.
So before checking if the fragmentation handling for this VNET is active, switch the VNET to the VNET of the interface to always get the one we want.
Reviewed by: hselasky MFC after: 3 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D22153
|