From: "Zach O'Keefe" <zokeefe@google.com>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again"
Date: Fri, 21 Jun 2024 10:26:34 -0700 [thread overview]
Message-ID: <CAAa6QmRdzoMuf3PyLcYP1X_uQAWj9_1mB0oD5dYpPT4hJqFHBw@mail.gmail.com> (raw)
In-Reply-To: <20240621144246.11148-1-jack@suse.cz>
On Fri, Jun 21, 2024 at 7:42 AM Jan Kara <jack@suse.cz> wrote:
>
> This reverts commit 9319b647902cbd5cc884ac08a8a6d54ce111fc78.
>
> The commit is broken in several ways. Firstly, the removed (u64) cast
> from the multiplication will introduce a multiplication overflow on
> 32-bit archs if wb_thresh * bg_thresh >= 1<<32 (which is actually common
> - the default settings with 4GB of RAM will trigger this). Secondly, the
> div64_u64() is unnecessarily expensive on 32-bit archs. We have
> div64_ul() in case we want to be safe & cheap. Thirdly, if dirty
> thresholds are larger than 1<<32 pages, then dirty balancing is
> going to blow up in many other spectacular ways anyway so trying to fix
> one possible overflow is just moot.
>
> CC: stable@vger.kernel.org
> Fixes: 9319b647902c ("mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again")
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> mm/page-writeback.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/page-writeback.c b/mm/page-writeback.c
> index 12c9297ed4a7..2573e2d504af 100644
> --- a/mm/page-writeback.c
> +++ b/mm/page-writeback.c
> @@ -1660,7 +1660,7 @@ static inline void wb_dirty_limits(struct dirty_throttle_control *dtc)
> */
> dtc->wb_thresh = __wb_calc_thresh(dtc, dtc->thresh);
> dtc->wb_bg_thresh = dtc->thresh ?
> - div64_u64(dtc->wb_thresh * dtc->bg_thresh, dtc->thresh) : 0;
> + div_u64((u64)dtc->wb_thresh * dtc->bg_thresh, dtc->thresh) : 0;
>
> /*
> * In order to avoid the stacked BDI deadlock we need
> --
> 2.35.3
>
>
Thanks Jan,
Reviewed-By: Zach O'Keefe <zokeefe@google.com>
next prev parent reply other threads:[~2024-06-21 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 14:42 [PATCH 0/2] mm: Avoid possible overflows in dirty throttling Jan Kara
2024-06-21 14:42 ` [PATCH 1/2] Revert "mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again" Jan Kara
2024-06-21 17:26 ` Zach O'Keefe [this message]
2024-06-21 14:42 ` [PATCH 2/2] mm: Avoid overflows in dirty throttling logic Jan Kara
2024-06-21 17:10 ` Andrew Morton
2024-06-21 17:29 ` Zach O'Keefe
2024-06-24 8:16 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAa6QmRdzoMuf3PyLcYP1X_uQAWj9_1mB0oD5dYpPT4hJqFHBw@mail.gmail.com \
--to=zokeefe@google.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox