Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:3 as permitted sender) client-ip=2620:137:e000::3:3;
From:   Jens Axboe <axboe@kernel.dk>
To:     Tejun Heo <tj@kernel.org>, Josef Bacik <josef@toxicpanda.com>,
        Khazhismel Kumykov <khazhy@chromium.org>
Cc:     Yu Kuai <yukuai3@huawei.com>, cgroups@vger.kernel.org,
        linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
        oleg@redhat.com, linan122@huawei.com,
        Khazhismel Kumykov <khazhy@google.com>
In-Reply-To: <20231020223617.2739774-1-khazhy@google.com>
References: <20231020223617.2739774-1-khazhy@google.com>
Subject: Re: [PATCH] blk-throttle: check for overflow in
 calculate_bytes_allowed
Message-Id: <169784872374.3020638.17698696801548218359.b4-ty@kernel.dk>
Date:   Fri, 20 Oct 2023 18:38:43 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk


On Fri, 20 Oct 2023 15:36:17 -0700, Khazhismel Kumykov wrote:
> Inexact, we may reject some not-overflowing values incorrectly, but
> they'll be on the order of exabytes allowed anyways.
> 
> This fixes divide error crash on x86 if bps_limit is not configured or
> is set too high in the rare case that jiffy_elapsed is greater than HZ.
> 
> 
> [...]

Applied, thanks!

[1/1] blk-throttle: check for overflow in calculate_bytes_allowed
      commit: 2dd710d476f2f1f6eaca884f625f69ef4389ed40

Best regards,
-- 
Jens Axboe