linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Maxim Patlasov <MPatlasov@parallels.com>
Cc: riel@redhat.com, linux-kernel@vger.kernel.org, mhocko@suse.cz,
	linux-mm@kvack.org, kosaki.motohiro@jp.fujitsu.com,
	fengguang.wu@intel.com, jweiner@redhat.com
Subject: Re: [PATCH] mm/page-writeback.c: fix divide by zero in bdi_dirty_limits
Date: Fri, 11 Jul 2014 15:27:32 -0700	[thread overview]
Message-ID: <20140711152732.de78603744cd861497eca5dc@linux-foundation.org> (raw)
In-Reply-To: <20140711081656.15654.19946.stgit@localhost.localdomain>

On Fri, 11 Jul 2014 12:18:27 +0400 Maxim Patlasov <MPatlasov@parallels.com> wrote:

> Under memory pressure, it is possible for dirty_thresh, calculated by
> global_dirty_limits() in balance_dirty_pages(), to equal zero.

Under what circumstances?  Really small values of vm_dirty_bytes?

> Then, if
> strictlimit is true, bdi_dirty_limits() tries to resolve the proportion:
> 
>   bdi_bg_thresh : bdi_thresh = background_thresh : dirty_thresh
> 
> by dividing by zero.
> 
> ...
>
> --- a/mm/page-writeback.c
> +++ b/mm/page-writeback.c
> @@ -1306,9 +1306,9 @@ static inline void bdi_dirty_limits(struct backing_dev_info *bdi,
>  	*bdi_thresh = bdi_dirty_limit(bdi, dirty_thresh);
>  
>  	if (bdi_bg_thresh)
> -		*bdi_bg_thresh = div_u64((u64)*bdi_thresh *
> -					 background_thresh,
> -					 dirty_thresh);
> +		*bdi_bg_thresh = dirty_thresh ? div_u64((u64)*bdi_thresh *
> +							background_thresh,
> +							dirty_thresh) : 0;

This introduces a peculiar discontinuity:

if dirty_thresh==3, treat it as 3
if dirty_thresh==2, treat it as 2
if dirty_thresh==1, treat it as 1
if dirty_thresh==0, treat it as infinity

Would it not make more sense to change global_dirty_limits() to convert
0 to 1?  With an appropriate comment, obviously.


Or maybe the fix lies elsewhere.  Please do tell us how this zero comes
about.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2014-07-11 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11  8:18 [PATCH] mm/page-writeback.c: fix divide by zero in bdi_dirty_limits Maxim Patlasov
2014-07-11 14:49 ` Rik van Riel
2014-07-11 22:27 ` Andrew Morton [this message]
2014-07-14  8:06   ` Maxim Patlasov

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=20140711152732.de78603744cd861497eca5dc@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=MPatlasov@parallels.com \
    --cc=fengguang.wu@intel.com \
    --cc=jweiner@redhat.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=riel@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).