bootchart: fix a potential buffer overrun

If the configured number of samples was close to MAXSAMPLES,
the samples buffer could be overrun:

- by 1, because of off-by-one in the condition (samples > arg_samples_len),
and
- by many in case of an overrun, because the number of samples to
  capture was increased, instead of being decreased.

Simplify things by converting to a normal for-loop.

In store.c: change buffer size from 4095 to 4096. 4095 is a strange
number.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek
2013-03-31 14:34:08 -04:00
parent 4cd5f79d0b
commit 522cd7f18b
2 changed files with 5 additions and 11 deletions
+4 -10
View File
@@ -288,7 +288,7 @@ int main(int argc, char *argv[]) {
log_uptime();
/* main program loop */
while (!exiting) {
for (samples = 0; !exiting && samples < arg_samples_len; samples++) {
int res;
double sample_stop;
struct timespec req;
@@ -315,7 +315,7 @@ int main(int argc, char *argv[]) {
NULL);
/* wait for /proc to become available, discarding samples */
if (!(graph_start > 0.0))
if (graph_start <= 0.0)
log_uptime();
else
log_sample(samples);
@@ -334,7 +334,7 @@ int main(int argc, char *argv[]) {
* we'll lose all the missed samples and overrun our total
* time
*/
if ((newint_ns > 0) || (newint_s > 0)) {
if (newint_ns > 0 || newint_s > 0) {
req.tv_sec = newint_s;
req.tv_nsec = newint_ns;
@@ -350,14 +350,8 @@ int main(int argc, char *argv[]) {
} else {
overrun++;
/* calculate how many samples we lost and scrap them */
arg_samples_len = arg_samples_len + ((int)(newint_ns / interval));
arg_samples_len -= (int)(newint_ns / interval);
}
samples++;
if (samples > arg_samples_len)
break;
}
/* do some cleanup, close fd's */
+1 -1
View File
@@ -114,7 +114,7 @@ static int pid_cmdline_strscpy(char *buffer, size_t buf_len, int pid) {
void log_sample(int sample) {
static int vmstat;
static int schedstat;
char buf[4095];
char buf[4096];
char key[256];
char val[256];
char rt[256];