All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: surenb@google.com, minchan@kernel.org, joelaf@google.com,
	lokeshgidra@google.com, kernel-team@android.com,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: mremap - Fix extent calculation
Date: Sat, 19 Dec 2020 09:51:51 -0800	[thread overview]
Message-ID: <20201219175151.GA6542@roeck-us.net> (raw)

On Sat, Dec 19, 2020 at 05:04:33PM +0000, Kalesh Singh wrote:
> When `next < old_addr`, `next - old_addr` arithmetic underflows
> causing `extent` to be incorrect.
> 
> Make `extent` the smaller of `next - old_addr` or `old_end - old_addr`.
> 
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Signed-off-by: Kalesh Singh <kaleshsingh@google.com>

This patch fixes the problem I had observed when booting 'parisc'
images.

Tested-by: Guenter Roeck <linux@roeck-us.net>

Guenter

> ---
>  mm/mremap.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/mremap.c b/mm/mremap.c
> index c5590afe7165..f554320281cc 100644
> --- a/mm/mremap.c
> +++ b/mm/mremap.c
> @@ -358,7 +358,9 @@ static unsigned long get_extent(enum pgt_entry entry, unsigned long old_addr,
>  
>  	next = (old_addr + size) & mask;
>  	/* even if next overflowed, extent below will be ok */
> -	extent = (next > old_end) ? old_end - old_addr : next - old_addr;
> +	extent = next - old_addr;
> +	if (extent > old_end - old_addr)
> +		extent = old_end - old_addr;
>  	next = (new_addr + size) & mask;
>  	if (extent > next - new_addr)
>  		extent = next - new_addr;
> -- 
> 2.29.2.729.g45daf8777d-goog
> 


             reply	other threads:[~2020-12-19 17:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 17:51 Guenter Roeck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-19 17:04 [PATCH] mm: mremap - Fix extent calculation Kalesh Singh
2020-12-19 17:04 ` Kalesh Singh

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=20201219175151.GA6542@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=joelaf@google.com \
    --cc=kaleshsingh@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lokeshgidra@google.com \
    --cc=minchan@kernel.org \
    --cc=surenb@google.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.