All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	sandeen@redhat.com, akpm@linux-foundation.org,
	jweiner@redhat.com, kosaki.motohiro@jp.fujitsu.com,
	fengguang.wu@intel.com, mpatlasov@parallels.com,
	Motohiro.Kosaki@us.fujitsu.com
Subject: [PATCH v3] mm,writeback: fix divide by zero in pos_ratio_polynom
Date: Wed, 30 Apr 2014 10:41:14 -0400	[thread overview]
Message-ID: <20140430104114.4bdc588e@cuia.bos.redhat.com> (raw)
In-Reply-To: <20140430134826.GH4357@dhcp22.suse.cz>

On Wed, 30 Apr 2014 15:48:26 +0200
Michal Hocko <mhocko@suse.cz> wrote:

> This is still prone to u64 -> s32 issue, isn't it?
> What was the original problem anyway? Was it really setpoint > limit or
> rather the overflow?

This patch should avoid math overflows with both the initial
subtraction, and with use of the truncated divisor by div_s64
and div_u64.

I added redundant casts in the div_s64 and div_u64 calls to
make it clear what those functions do internally, which should
make it easy to understand why we do the same cast in the if
statements right above.

I believe this version of the patch addresses everybody's concerns.

---8<---

Subject: mm,writeback: fix divide by zero in pos_ratio_polynom

It is possible for "limit - setpoint + 1" to equal zero, leading to a
divide by zero error. Blindly adding 1 to "limit - setpoint" is not
working, so we need to actually test the divisor before calling div64.

Signed-off-by: Rik van Riel <riel@redhat.com>
---
 mm/page-writeback.c | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/mm/page-writeback.c b/mm/page-writeback.c
index ef41349..6405687 100644
--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -598,10 +598,15 @@ static inline long long pos_ratio_polynom(unsigned long setpoint,
 					  unsigned long limit)
 {
 	long long pos_ratio;
+	long divisor;
 	long x;
 
+	divisor = limit - setpoint;
+	if (!(s32)divisor)
+		divisor = 1;	/* Avoid div-by-zero */
+
 	x = div_s64(((s64)setpoint - (s64)dirty) << RATELIMIT_CALC_SHIFT,
-		    limit - setpoint + 1);
+		    (s32)divisor);
 	pos_ratio = x;
 	pos_ratio = pos_ratio * x >> RATELIMIT_CALC_SHIFT;
 	pos_ratio = pos_ratio * x >> RATELIMIT_CALC_SHIFT;
@@ -842,8 +847,12 @@ static unsigned long bdi_position_ratio(struct backing_dev_info *bdi,
 	x_intercept = bdi_setpoint + span;
 
 	if (bdi_dirty < x_intercept - span / 4) {
+		unsigned long divisor = x_intercept - bdi_setpoint;
+		if (!(u32)divisor)
+			divisor = 1;	/* Avoid div-by-zero */
+
 		pos_ratio = div_u64(pos_ratio * (x_intercept - bdi_dirty),
-				    x_intercept - bdi_setpoint + 1);
+				    (u32)divisor);
 	} else
 		pos_ratio /= 4;
 

WARNING: multiple messages have this Message-ID (diff)
From: Rik van Riel <riel@redhat.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	sandeen@redhat.com, akpm@linux-foundation.org,
	jweiner@redhat.com, kosaki.motohiro@jp.fujitsu.com,
	fengguang.wu@intel.com, mpatlasov@parallels.com,
	Motohiro.Kosaki@us.fujitsu.com
Subject: [PATCH v3] mm,writeback: fix divide by zero in pos_ratio_polynom
Date: Wed, 30 Apr 2014 10:41:14 -0400	[thread overview]
Message-ID: <20140430104114.4bdc588e@cuia.bos.redhat.com> (raw)
In-Reply-To: <20140430134826.GH4357@dhcp22.suse.cz>

On Wed, 30 Apr 2014 15:48:26 +0200
Michal Hocko <mhocko@suse.cz> wrote:

> This is still prone to u64 -> s32 issue, isn't it?
> What was the original problem anyway? Was it really setpoint > limit or
> rather the overflow?

This patch should avoid math overflows with both the initial
subtraction, and with use of the truncated divisor by div_s64
and div_u64.

I added redundant casts in the div_s64 and div_u64 calls to
make it clear what those functions do internally, which should
make it easy to understand why we do the same cast in the if
statements right above.

I believe this version of the patch addresses everybody's concerns.

---8<---

Subject: mm,writeback: fix divide by zero in pos_ratio_polynom

It is possible for "limit - setpoint + 1" to equal zero, leading to a
divide by zero error. Blindly adding 1 to "limit - setpoint" is not
working, so we need to actually test the divisor before calling div64.

Signed-off-by: Rik van Riel <riel@redhat.com>
---
 mm/page-writeback.c | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/mm/page-writeback.c b/mm/page-writeback.c
index ef41349..6405687 100644
--- a/mm/page-writeback.c
+++ b/mm/page-writeback.c
@@ -598,10 +598,15 @@ static inline long long pos_ratio_polynom(unsigned long setpoint,
 					  unsigned long limit)
 {
 	long long pos_ratio;
+	long divisor;
 	long x;
 
+	divisor = limit - setpoint;
+	if (!(s32)divisor)
+		divisor = 1;	/* Avoid div-by-zero */
+
 	x = div_s64(((s64)setpoint - (s64)dirty) << RATELIMIT_CALC_SHIFT,
-		    limit - setpoint + 1);
+		    (s32)divisor);
 	pos_ratio = x;
 	pos_ratio = pos_ratio * x >> RATELIMIT_CALC_SHIFT;
 	pos_ratio = pos_ratio * x >> RATELIMIT_CALC_SHIFT;
@@ -842,8 +847,12 @@ static unsigned long bdi_position_ratio(struct backing_dev_info *bdi,
 	x_intercept = bdi_setpoint + span;
 
 	if (bdi_dirty < x_intercept - span / 4) {
+		unsigned long divisor = x_intercept - bdi_setpoint;
+		if (!(u32)divisor)
+			divisor = 1;	/* Avoid div-by-zero */
+
 		pos_ratio = div_u64(pos_ratio * (x_intercept - bdi_dirty),
-				    x_intercept - bdi_setpoint + 1);
+				    (u32)divisor);
 	} else
 		pos_ratio /= 4;
 

--
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-04-30 14:43 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 19:19 [PATCH] mm,writeback: fix divide by zero in pos_ratio_polynom Rik van Riel
2014-04-29 19:19 ` Rik van Riel
2014-04-29 19:43 ` Motohiro Kosaki
2014-04-29 19:43   ` Motohiro Kosaki
2014-04-29 22:39 ` Andrew Morton
2014-04-29 22:39   ` Andrew Morton
2014-04-29 22:48   ` Rik van Riel
2014-04-29 22:48     ` Rik van Riel
2014-04-29 22:53     ` Andrew Morton
2014-04-29 22:53       ` Andrew Morton
2014-04-30  8:04 ` Maxim Patlasov
2014-04-30  8:04   ` Maxim Patlasov
2014-04-30  8:12   ` Michal Hocko
2014-04-30  8:12     ` Michal Hocko
2014-04-30  8:34     ` Maxim Patlasov
2014-04-30  8:34       ` Maxim Patlasov
2014-04-30 10:01 ` Masayoshi Mizuma
2014-04-30 10:01   ` Masayoshi Mizuma
2014-04-30 13:30   ` [PATCH v2] " Rik van Riel
2014-04-30 13:30     ` Rik van Riel
2014-04-30 13:48     ` Michal Hocko
2014-04-30 13:48       ` Michal Hocko
2014-04-30 14:26       ` Rik van Riel
2014-04-30 14:26         ` Rik van Riel
2014-04-30 14:31       ` Rik van Riel
2014-04-30 14:31         ` Rik van Riel
2014-04-30 14:49         ` Michal Hocko
2014-04-30 14:49           ` Michal Hocko
2014-04-30 14:52           ` Rik van Riel
2014-04-30 14:52             ` Rik van Riel
2014-04-30 14:41       ` Rik van Riel [this message]
2014-04-30 14:41         ` [PATCH v3] " Rik van Riel
2014-04-30 19:00         ` Andrew Morton
2014-04-30 19:00           ` Andrew Morton
2014-04-30 19:30           ` Rik van Riel
2014-04-30 19:30             ` Rik van Riel
2014-04-30 19:35             ` Andrew Morton
2014-04-30 19:35               ` Andrew Morton
2014-04-30 20:02               ` [PATCH v4] " Rik van Riel
2014-04-30 20:02                 ` Rik van Riel
2014-04-30 20:13                 ` Andrew Morton
2014-04-30 20:13                   ` Andrew Morton
2014-04-30 20:32                   ` Rik van Riel
2014-04-30 20:32                     ` Rik van Riel
2014-04-30 20:42                   ` [PATCH v5] " Rik van Riel
2014-04-30 20:42                     ` Rik van Riel
2014-04-30 21:00                     ` Andrew Morton
2014-04-30 21:00                       ` Andrew Morton
2014-04-30 21:21                       ` Rik van Riel
2014-04-30 21:21                         ` Rik van Riel
2014-04-30 21:32                     ` Andrew Morton
2014-04-30 21:32                       ` Andrew Morton
2014-05-02  9:16                     ` Michal Hocko
2014-05-02  9:16                       ` Michal Hocko
2014-05-08 10:17                     ` Masayoshi Mizuma
2014-05-08 10:17                       ` Masayoshi Mizuma

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=20140430104114.4bdc588e@cuia.bos.redhat.com \
    --to=riel@redhat.com \
    --cc=Motohiro.Kosaki@us.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --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=m.mizuma@jp.fujitsu.com \
    --cc=mhocko@suse.cz \
    --cc=mpatlasov@parallels.com \
    --cc=sandeen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.