Searched hist:"0 e1152fcc2fe48dea2583ac89d30ba77b4ab78cc" (Results 1 – 8 of 8) sorted by relevance
/freebsd/sys/kern/ |
H A D | kern_ffclock.c | diff 0e1152fcc2fe48dea2583ac89d30ba77b4ab78cc Tue Oct 28 13:00:39 CET 2014 Hans Petter Selasky <hselasky@FreeBSD.org> The SYSCTL data pointers can come from userspace and must not be directly accessed. Although this will work on some platforms, it can throw an exception if the pointer is invalid and then panic the kernel.
Add a missing SYSCTL_IN() of "SCTP_BASE_STATS" structure.
MFC after: 3 days Sponsored by: Mellanox Technologies
|
/freebsd/sys/netinet/cc/ |
H A D | cc.c | diff 0e1152fcc2fe48dea2583ac89d30ba77b4ab78cc Tue Oct 28 13:00:39 CET 2014 Hans Petter Selasky <hselasky@FreeBSD.org> The SYSCTL data pointers can come from userspace and must not be directly accessed. Although this will work on some platforms, it can throw an exception if the pointer is invalid and then panic the kernel.
Add a missing SYSCTL_IN() of "SCTP_BASE_STATS" structure.
MFC after: 3 days Sponsored by: Mellanox Technologies
|
/freebsd/sys/dev/acpi_support/ |
H A D | acpi_ibm.c | diff 0e1152fcc2fe48dea2583ac89d30ba77b4ab78cc Tue Oct 28 13:00:39 CET 2014 Hans Petter Selasky <hselasky@FreeBSD.org> The SYSCTL data pointers can come from userspace and must not be directly accessed. Although this will work on some platforms, it can throw an exception if the pointer is invalid and then panic the kernel.
Add a missing SYSCTL_IN() of "SCTP_BASE_STATS" structure.
MFC after: 3 days Sponsored by: Mellanox Technologies
|
/freebsd/sys/dev/asmc/ |
H A D | asmc.c | diff 0e1152fcc2fe48dea2583ac89d30ba77b4ab78cc Tue Oct 28 13:00:39 CET 2014 Hans Petter Selasky <hselasky@FreeBSD.org> The SYSCTL data pointers can come from userspace and must not be directly accessed. Although this will work on some platforms, it can throw an exception if the pointer is invalid and then panic the kernel.
Add a missing SYSCTL_IN() of "SCTP_BASE_STATS" structure.
MFC after: 3 days Sponsored by: Mellanox Technologies
|
/freebsd/sys/netinet/ |
H A D | siftr.c | diff 0e1152fcc2fe48dea2583ac89d30ba77b4ab78cc Tue Oct 28 13:00:39 CET 2014 Hans Petter Selasky <hselasky@FreeBSD.org> The SYSCTL data pointers can come from userspace and must not be directly accessed. Although this will work on some platforms, it can throw an exception if the pointer is invalid and then panic the kernel.
Add a missing SYSCTL_IN() of "SCTP_BASE_STATS" structure.
MFC after: 3 days Sponsored by: Mellanox Technologies
|
H A D | sctp_sysctl.c | diff 0e1152fcc2fe48dea2583ac89d30ba77b4ab78cc Tue Oct 28 13:00:39 CET 2014 Hans Petter Selasky <hselasky@FreeBSD.org> The SYSCTL data pointers can come from userspace and must not be directly accessed. Although this will work on some platforms, it can throw an exception if the pointer is invalid and then panic the kernel.
Add a missing SYSCTL_IN() of "SCTP_BASE_STATS" structure.
MFC after: 3 days Sponsored by: Mellanox Technologies
|
/freebsd/sys/net/ |
H A D | bpf.c | diff 0e1152fcc2fe48dea2583ac89d30ba77b4ab78cc Tue Oct 28 13:00:39 CET 2014 Hans Petter Selasky <hselasky@FreeBSD.org> The SYSCTL data pointers can come from userspace and must not be directly accessed. Although this will work on some platforms, it can throw an exception if the pointer is invalid and then panic the kernel.
Add a missing SYSCTL_IN() of "SCTP_BASE_STATS" structure.
MFC after: 3 days Sponsored by: Mellanox Technologies
|
/freebsd/sys/dev/acpica/ |
H A D | acpi.c | diff 0e1152fcc2fe48dea2583ac89d30ba77b4ab78cc Tue Oct 28 13:00:39 CET 2014 Hans Petter Selasky <hselasky@FreeBSD.org> The SYSCTL data pointers can come from userspace and must not be directly accessed. Although this will work on some platforms, it can throw an exception if the pointer is invalid and then panic the kernel.
Add a missing SYSCTL_IN() of "SCTP_BASE_STATS" structure.
MFC after: 3 days Sponsored by: Mellanox Technologies
|