Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.33 as permitted sender) client-ip=23.128.96.33;
MIME-Version: 1.0
References: <20230922230535.296350-1-joshdon@google.com> <20230922230535.296350-2-joshdon@google.com>
 <ZRALk+fMpW5895fF@gmail.com>
In-Reply-To: <ZRALk+fMpW5895fF@gmail.com>
From:   Josh Don <joshdon@google.com>
Date:   Mon, 25 Sep 2023 09:38:39 -0700
Message-ID: <CABk29Ntm1aK-f5t8cDY5DoBc_LwYqymWkPau0mVAOOaO4Ac4hw@mail.gmail.com>
Subject: Re: [PATCH 2/2] sched: fix warning in bandwidth distribution
To:     Ingo Molnar <mingo@kernel.org>
Cc:     Ingo Molnar <mingo@redhat.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Juri Lelli <juri.lelli@redhat.com>,
        Vincent Guittot <vincent.guittot@linaro.org>,
        Dietmar Eggemann <dietmar.eggemann@arm.com>,
        Steven Rostedt <rostedt@goodmis.org>,
        Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
        Daniel Bristot de Oliveira <bristot@redhat.com>,
        Valentin Schneider <vschneid@redhat.com>,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

> When the warning hits, we don't have any other side-effects,
> such as bad behavior or data corruption, correct?

Correct, the warning is benign.

> Under that assumption I've queued your fix in tip:sched/core,
> for a v6.7 merge, and not in tip:sched/urgent for a v6.6 merge,
> but let me know if I'm reading the code wrong...

Thanks Ingo!