openafs/tests
Cheyenne Wills bf37aec672 tests: fix potential divide by zero condition
Running clang's static analysis revealed a possible divide by zero
condition.

There is a random chance of the divide by zero.

- it has to be in the first pass of the main loop testing events
  (counter = 0)
- 90% chance path :   if (counter < (NUMEVENTS -1) &&
                          random() % 10 == 0)      -- needs to be false
- 25% chance path:    if (random() % 4 == 0)       -- needs to be true

if the above conditions are met, the statement
    int victim = random() % counter
is a divide by zero.

Add a check to ensure the counter is greater than zero.  Add a comment
to document that only events prior to the current event are randomly
selected.

Change-Id: I4b4e73fa324842bb504bcc952079af15aea8a6a3
Reviewed-on: https://gerrit.openafs.org/14501
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Reviewed-by: Michael Meffie <mmeffie@sinenomine.net>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
2021-01-22 19:36:36 -05:00
..
auth Move key-related warnings to common server code 2021-01-08 12:11:37 -05:00
bozo tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
bucoord tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
cmd tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
common Move key-related warnings to common server code 2021-01-08 12:11:37 -05:00
kauth tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
opr tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
ptserver tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
rpctestlib Remove dead code 2019-08-23 09:36:44 -04:00
rx tests: fix potential divide by zero condition 2021-01-22 19:36:36 -05:00
tap tests: Start using the upstream C TAP harness 2012-05-11 16:36:44 -07:00
tests-lib/perl5 tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
util tests: Fix most tests for objdir builds 2019-12-13 00:03:21 -05:00
venus tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
volser tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
.gitignore tests: Add core to .gitignore in tests 2020-03-20 15:56:12 -04:00
libwrap tests: use exec to call libwrap'd executables 2016-12-16 16:25:58 -05:00
Makefile.in tests: Accommodate c-tap-harness 4.7 2020-08-20 22:36:56 -04:00
README correct whitespace errors in readme files 2013-01-07 07:40:46 -08:00
TESTS tests: Modernize writekeyfile.c 2020-06-19 11:48:57 -04:00

This directory contains a test harness and the beginnings of what is
intended to become the primary OpenAFS test suite.  The tests in this
directory are run when "make check" is run at the top level of the OpenAFS
tree.

runtests is the test harness, and TESTS is the list of tests that it
will run.  If you add a new test, add it to TESTS as well.  All tests must
be executables (possibly shell scripts or Perl scripts) that end in either
".t" or "-t", but should be listed in TESTS without that suffix.

Tests should be organized into subdirectories, and where it makes sense to
do so, those subdirectories should match the subdirectory names under src
in the AFS source tree.  In other words, tests for src/util/* should go in
a directory named util, tests for the libkopenafs library should go in a
directory named kopenafs, and so forth.  To integrate with the build
system, each subdirectory will need to have its own Makefile.in and be
added to the list of generated Makefiles in configure.in at the top
level.   The Makefile.in in this directory will also need to be modified
to recurse into any new directories.  See util/Makefile.in for an example
of how to write a Makefile.in for a new test directory.

The files comprising the test harness are sourced from the C TAP Harness
distribution using the src/external mechanism. The upstream site for that
distribution is at:

    http://www.eyrie.org/~eagle/software/c-tap-harness/

but feel free to propose modifications directly through OpenAFS Gerrit.
Russ Allbery will take care of merging modifications upstream.  However,
OpenAFS-specific modifications should not be made to those files.  To add
additional OpenAFS-specific code to the TAP library, add additional *.c
and *.h (or *.sh) files to the tests/tap directory rather than modifying files
in src/external.

More information can be found in the HOWTO contained in
src/external/c-tap-harness/HOWTO