[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1316011547.5040.22.camel@twins>
Date: Wed, 14 Sep 2011 16:45:47 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Robert Richter <robert.richter@....com>
Cc: Ingo Molnar <mingo@...e.hu>, Stephane Eranian <eranian@...gle.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] perf, x86: Fix event scheduler for constraints with
On Sat, 2011-09-10 at 16:49 +0200, Robert Richter wrote:
> struct perf_sched {
> int max_weight;
> int max_events;
> struct event_constraint **constraints;
> struct sched_state state;
> +
> + int saved_states;
This creates an ugly hole in the structure
> + struct sched_state saved[SCHED_STATES_MAX];
> };
>
> static void perf_sched_init(struct perf_sched *sched, struct event_constraint **c,
> @@ -817,7 +849,30 @@ static void perf_sched_init(struct perf_sched *sched, struct event_constraint **
> sched->state.unassigned = num;
> }
>
> -static struct sched_state *perf_sched_find_counter(struct perf_sched *sched)
> +static void perf_sched_save_state(struct perf_sched *sched)
> +{
> + if (sched->saved_states >= SCHED_STATES_MAX)
> + return;
> +
> + sched->saved[sched->saved_states] = sched->state;
> + sched->saved_states++;
> +}
Shouldn't we fail the save_state when we're out of states? the restore
code doesn't check to see if --saved_states is within range and simply
derefs the array.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists