zfs/scripts
Brian Behlendorf 10715a0187 Add default stack checking
When your kernel is built with kernel stack tracing enabled and you
have the debugfs filesystem mounted.  Then the zfs.sh script will clear
the worst observed kernel stack depth on module load and check the worst
case usage on module removal.  If the stack depth ever exceeds 7000
bytes the full stack will be printed for debugging.  This is dangerously
close to overrunning the default 8k stack.

This additional advisory debugging is particularly valuable when running
the regression tests on a kernel built with 16k stacks.  In this case,
almost no matter how bad the stack overrun is you will see be able to
get a clean stack trace for debugging.  Since the worst case stack usage
can be highly variable it's helpful to always check the worst case usage.
2011-06-13 13:50:21 -07:00
..
zpios-profile Fix 'zfs set volsize=N pool/dataset' 2011-05-02 08:54:40 -07:00
zpios-test Fix 'zfs set volsize=N pool/dataset' 2011-05-02 08:54:40 -07:00
zpool-config Delay before destroying loopback devices 2011-06-03 14:38:25 -07:00
zpool-layout Fix 'zfs set volsize=N pool/dataset' 2011-05-02 08:54:40 -07:00
Makefile.am Remove spl/zfs modules as part of cleanup 2010-11-11 11:40:06 -08:00
Makefile.in Fix 'zfs set volsize=N pool/dataset' 2011-05-02 08:54:40 -07:00
common.sh.in Add default stack checking 2011-06-13 13:50:21 -07:00
zconfig.sh Pass -f option for import 2011-06-10 11:21:31 -07:00
zfault.sh Remove partition from vdev name in zfault.sh 2010-11-29 10:53:53 -08:00
zfs.sh Add default stack checking 2011-06-13 13:50:21 -07:00
zpios-sanity.sh Sanatize zpios-sanity.sh environment 2011-06-03 15:08:49 -07:00
zpios-survey.sh Add linux zpios support 2010-08-31 13:42:01 -07:00
zpios.sh Always unload zpios.ko on exit 2011-06-02 10:25:35 -07:00
zpool-create.sh Add build system 2010-08-31 13:41:27 -07:00