Skip to content
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.

Module parameter to enable spl_panic() to panic the kernel #634

Merged
merged 1 commit into from
Jul 26, 2017

Conversation

verygreen
Copy link
Contributor

In unattended operations it's often more useful to have node
panic and reboot when it encounters problems as opposed to
sit there indefinitely waiting for somebody to discover it.

This implements an spl_panic_crash module parameter, set it
to nonzero to cause spl_panic() to call panic().

Signed-off-by: Oleg Drokin [email protected]

In unattended operations it's often more useful to have node
panic and reboot when it encounters problems as opposed to
sit there indefinitely waiting for somebody to discover it.

This implements an spl_panic_crash module parameter, set it
to nonzero to cause spl_panic() to call panic().

Signed-off-by: Oleg Drokin <[email protected]>
@loli10K
Copy link
Contributor

loli10K commented Jul 25, 2017

I've found myself wanting this for a while now, and i've always resorted to patching spl_panic() when i needed it (or using systemtap, which is boring in this case).

Copy link
Contributor

@behlendorf behlendorf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@bunder2015
Copy link

bunder2015 commented Jul 26, 2017

Does this cover all instances where zfs/spl would panic, or just the spl ones? I've come across instances where zfs panicked and the system kept running (sometimes without available pool io) until I hard rebooted. eg openzfs/zfs#6315

@verygreen
Copy link
Contributor Author

This covers all cases where spl_panic() is called via various assertions.

ZFS assertions are still done via spl I am sure.

@behlendorf behlendorf merged commit 410f7ab into openzfs:master Jul 26, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants