Page MenuHomeFreeBSD

Check for excessively small times in kern_clock_settime().
ClosedPublic

Authored by markj on May 3 2019, 4:05 PM.
Tags
None
Referenced Files
F138016029: D20151.id57019.diff
Fri, Nov 28, 4:34 AM
F137963615: D20151.id57012.diff
Thu, Nov 27, 5:47 PM
Unknown Object (File)
Tue, Nov 25, 6:13 AM
Unknown Object (File)
Tue, Nov 25, 1:59 AM
Unknown Object (File)
Sat, Nov 22, 11:55 PM
Unknown Object (File)
Fri, Nov 21, 4:29 AM
Unknown Object (File)
Mon, Nov 17, 6:17 PM
Unknown Object (File)
Mon, Nov 17, 1:45 AM
Subscribers
None

Details

Summary

This addresses a panic hit by syzkaller if wall_cmos_clock is set.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

If this causes a panic, maybe it shouldn't be conditional on allow_insane_settime? After all, syzkaller may eventually discovered sysctls.

Otherwise, LGTM.

This revision is now accepted and ready to land.May 3 2019, 4:37 PM
In D20151#433908, @cem wrote:

If this causes a panic, maybe it shouldn't be conditional on allow_insane_settime? After all, syzkaller may eventually discovered sysctls.

The commit log message for r312702 hints that allow_insane_settime already prevents a privileged user from panicking the system.

syzkaller would probably discover debug.kdb.panic first. :)

I forget why we left that knob, then. :)

This revision was automatically updated to reflect the committed changes.