You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LKRG protects some of its most critical variables by keeping them on a read-only page most of the time. Net is currently written as a somewhat-separate module that isn't similarly hardened - maybe it should eventually be hardened.
Also, maybe the kernel's data structures that we depend on (the printk ring buffer, the struct file for our reads from /dev/kmsg, etc.) should also be hardened (but how? we could detect corruption, but what we're to do on it besides panic when we know our logging is broken?) - or maybe that's a reason to move to (or introduce as duplicate/redundant) our own data structures eventually.
The text was updated successfully, but these errors were encountered:
Nov 10, 2022
LKRG protects some of its most critical variables by keeping them on a read-only page most of the time. Net is currently written as a somewhat-separate module that isn't similarly hardened - maybe it should eventually be hardened.
Also, maybe the kernel's data structures that we depend on (the
printk
ring buffer, thestruct file
for our reads from/dev/kmsg
, etc.) should also be hardened (but how? we could detect corruption, but what we're to do on it besides panic when we know our logging is broken?) - or maybe that's a reason to move to (or introduce as duplicate/redundant) our own data structures eventually.The text was updated successfully, but these errors were encountered: