public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Uladzislau Rezki <urezki@gmail.com>
To: shivamkalra98@zohomail.in
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Uladzislau Rezki <urezki@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Alice Ryhl <aliceryhl@google.com>,
	Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v12 3/5] mm/vmalloc: use physical page count in vread_iter()
Date: Wed, 6 May 2026 20:28:23 +0200	[thread overview]
Message-ID: <afuIR08cj0e7hpd0@pc636> (raw)
In-Reply-To: <20260428-vmalloc-shrink-v12-3-3c18c9172eb1@zohomail.in>

On Tue, Apr 28, 2026 at 01:54:18AM +0530, Shivam Kalra via B4 Relay wrote:
> From: Shivam Kalra <shivamkalra98@zohomail.in>
> 
> Update vread_iter() to derive the vm area size from vm->nr_pages rather
> than get_vm_area_size().
> 
> Currently both values are equivalent, but the upcoming vrealloc() shrink
> functionality will free pages without reducing the virtual reservation
> size. After such a shrink, the old get_vm_area_size() based calculation
> would overestimate the mapped range, causing vread_iter() to attempt
> reading from unmapped addresses. Switch to vm->nr_pages now so the
> reader remains correct once shrink support is added.
> 
> Signed-off-by: Shivam Kalra <shivamkalra98@zohomail.in>
> ---
>  mm/vmalloc.c | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/mm/vmalloc.c b/mm/vmalloc.c
> index 9cb3e287a1e8..65e0a23efb3b 100644
> --- a/mm/vmalloc.c
> +++ b/mm/vmalloc.c
> @@ -4661,7 +4661,14 @@ long vread_iter(struct iov_iter *iter, const char *addr, size_t count)
>  		smp_rmb();
>  
>  		vaddr = (char *) va->va_start;
> -		size = vm ? get_vm_area_size(vm) : va_size(va);
> +		if (vm)
> +			/*
> +			 * Cannot use get_vm_area_size() because realloc()
> +			 * may shrink the mapping and area->size may be outdated.
> +			 */
> +			size = vm->nr_pages << PAGE_SHIFT;
> +		else
> +			size = va_size(va);
>  
>  		if (addr >= vaddr + size)
>  			goto next_va;
> 
> -- 
> 2.43.0
> 
> 
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>

--
Uladzislau Rezki

  reply	other threads:[~2026-05-06 18:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 20:24 [PATCH v12 0/5] mm/vmalloc: free unused pages on vrealloc() shrink Shivam Kalra via B4 Relay
2026-04-27 20:24 ` [PATCH v12 1/5] mm/vmalloc: extract vm_area_free_pages() helper from vfree() Shivam Kalra via B4 Relay
2026-05-06 18:32   ` Uladzislau Rezki
2026-04-27 20:24 ` [PATCH v12 2/5] mm/vmalloc: use physical page count for vrealloc() grow-in-place check Shivam Kalra via B4 Relay
2026-05-06 18:47   ` Uladzislau Rezki
2026-05-06 19:43     ` Shivam Kalra
2026-04-27 20:24 ` [PATCH v12 3/5] mm/vmalloc: use physical page count in vread_iter() Shivam Kalra via B4 Relay
2026-05-06 18:28   ` Uladzislau Rezki [this message]
2026-04-27 20:24 ` [PATCH v12 4/5] mm/vmalloc: free unused pages on vrealloc() shrink Shivam Kalra via B4 Relay
2026-05-06 18:27   ` Uladzislau Rezki
2026-04-27 20:24 ` [PATCH v12 5/5] lib/test_vmalloc: add vrealloc test case Shivam Kalra via B4 Relay
2026-05-05 15:42 ` [PATCH v12 0/5] mm/vmalloc: free unused pages on vrealloc() shrink Shivam Kalra

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=afuIR08cj0e7hpd0@pc636 \
    --to=urezki@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=dakr@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shivamkalra98@zohomail.in \
    /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