update fuzz function names in docs with golang naming convention

Signed-off-by: Jiongchi Yu <jcyu.2022@phdcs.smu.edu.sg>
This commit is contained in:
TTFISH 2023-02-06 17:59:07 +08:00
parent 904a87d26d
commit 5bc3fea621

View File

@ -325,8 +325,8 @@ func newContainer(client *containerd.Client, f *fuzz.ConsumeFuzzer, ctx context.
return nil, errors.New("Could not create container") return nil, errors.New("Could not create container")
} }
// doFuzz() implements the logic of FuzzCreateContainerNoTearDown() // doFuzz() implements the logic of FuzzIntegCreateContainerNoTearDown()
// and FuzzCreateContainerWithTearDown() and allows for // and FuzzIntegCreateContainerWithTearDown() and allows for
// the option to turn on/off teardown after each iteration. // the option to turn on/off teardown after each iteration.
// From a high level it: // From a high level it:
// - Creates a client // - Creates a client
@ -395,9 +395,9 @@ func doFuzz(data []byte, shouldTearDown bool) int {
return 1 return 1
} }
// FuzzNoTearDownWithDownload() implements a fuzzer // FuzzIntegNoTearDownWithDownload() implements a fuzzer
// similar to FuzzCreateContainerNoTearDown() and // similar to FuzzIntegCreateContainerNoTearDown() and
// FuzzCreateContainerWithTearDown(), but it takes a // FuzzIntegCreateContainerWithTearDown(), but it takes a
// different approach to the initialization. Where // different approach to the initialization. Where
// the other 2 fuzzers depend on the containerd binaries // the other 2 fuzzers depend on the containerd binaries
// that were built manually, this fuzzer downloads them // that were built manually, this fuzzer downloads them
@ -416,8 +416,8 @@ func FuzzIntegNoTearDownWithDownload(data []byte) int {
return ret return ret
} }
// FuzzCreateContainerNoTearDown() implements a fuzzer // FuzzIntegCreateContainerNoTearDown() implements a fuzzer
// similar to FuzzCreateContainerWithTearDown() with // similar to FuzzIntegCreateContainerWithTearDown() with
// with one minor distinction: One tears down the // with one minor distinction: One tears down the
// daemon after each iteration whereas the other doesn't. // daemon after each iteration whereas the other doesn't.
// The two fuzzers' performance will be compared over time. // The two fuzzers' performance will be compared over time.
@ -432,9 +432,9 @@ func FuzzIntegCreateContainerNoTearDown(data []byte) int {
return ret return ret
} }
// FuzzCreateContainerWithTearDown() is similar to // FuzzIntegCreateContainerWithTearDown() is similar to
// FuzzCreateContainerNoTearDown() except that // FuzzIntegCreateContainerNoTearDown() except that
// FuzzCreateContainerWithTearDown tears down the daemon // FuzzIntegCreateContainerWithTearDown tears down the daemon
// after each iteration. // after each iteration.
func FuzzIntegCreateContainerWithTearDown(data []byte) int { func FuzzIntegCreateContainerWithTearDown(data []byte) int {
if !haveInitialized { if !haveInitialized {