ocfs2console: array index out of bounds risk in testing code

[Byte-Jerry]

There is a risk of array index out of bounds in the main functions of files blkid/cache.c, blkid/save.c, and blkid/read.c. When argc is greater than 2, the test program prints an error log and exits. If the second parameter is not entered when executing the command, argc is 1 and the parameter verification can be passed. In the following code, an array index out of bounds error occurs when using argv[1] to obtain a value.

For example, in the code in blkid/save.c, if argc equals 1, the array index is out of bounds on line 182.

#ifdef TEST_PROGRAM
int main(int argc, char **argv)
{
	blkid_cache cache = NULL;
	int ret;

	blkid_debug_mask = DEBUG_ALL;
	if (argc > 2) {
		fprintf(stderr, "Usage: %s [filename]\n"
			"Test loading/saving a cache (filename)\n", argv[0]);
		exit(1);
	}

	if ((ret = blkid_get_cache(&cache, "/dev/null")) != 0) {
		fprintf(stderr, "%s: error creating cache (%d)\n",
			argv[0], ret);
		exit(1);
	}
	if ((ret = blkid_probe_all(cache)) < 0) {
		fprintf(stderr, "error (%d) probing devices\n", ret);
		exit(1);
	}
	cache->bic_filename = blkid_strdup(argv[1]); //  line 182
	
	if ((ret = blkid_flush_cache(cache)) < 0) {
		fprintf(stderr, "error (%d) saving cache\n", ret);
		exit(1);
	}

	blkid_put_cache(cache);

	return ret;
}
#endif

I think the '>' in these main functions should be replaced with '<', which means the number of parameters must be greater than or equal to 2.