From: Andrew Morton <akpm@linux-foundation.org>
To: Artem Lytkin <iprintercanon@gmail.com>
Cc: linux-mm@kvack.org, urezki@gmail.com, willy@infradead.org,
shivamkalra98@zohomail.in, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] mm/vmalloc: stop truncating byte counts derived from nr_pages
Date: Thu, 30 Jul 2026 13:09:23 -0700 [thread overview]
Message-ID: <20260730130923.9e71be5f477ee3db333cf0f8@linux-foundation.org> (raw)
In-Reply-To: <20260730090628.65814-1-iprintercanon@gmail.com>
On Thu, 30 Jul 2026 12:06:25 +0300 Artem Lytkin <iprintercanon@gmail.com> wrote:
> Andrew asked for a v2 of the nr_pages widening, rebased on mm-new, with
> the changelog clarified on what has actually been observed.
>
> The widening reverts the two casts added by the patches I sent on 25
> July, so it needs those in the tree first, and they are not in mm-new,
> mm-unstable or mm-hotfixes-unstable today. They are here as 1/3 and 2/3 so
> that the series applies and Sashiko can chew on it. 2/3 is byte for byte
> what I sent; 1/3 has one corrected sentence in its changelog and the same
> one-line diff.
Sashiko couldn't apply it for some reason.
This all seems far too complex for such an obscure issue.
How about we queue just a single switch-to-ulong patch, add that to 7.3
and give it a Fixes:0bca23804632/cc:stable so 7.2.x gets fixed later?
next prev parent reply other threads:[~2026-07-30 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 17:57 [PATCH] mm/vmalloc: make vm_struct.nr_pages an unsigned long Artem Lytkin
2026-07-29 18:28 ` Matthew Wilcox
2026-07-29 21:45 ` Andrew Morton
2026-07-30 9:07 ` Artem Lytkin
2026-07-30 9:06 ` [PATCH v2 0/3] mm/vmalloc: stop truncating byte counts derived from nr_pages Artem Lytkin
2026-07-30 17:11 ` [PATCH v3] mm/vmalloc: make vm_struct.nr_pages an unsigned long Artem Lytkin
2026-07-30 20:09 ` Andrew Morton [this message]
2026-07-30 9:06 ` [PATCH v2 1/3] mm/vmalloc: fix 32-bit truncation of the area size in vread_iter() Artem Lytkin
2026-07-30 9:06 ` [PATCH v2 2/3] mm/vmalloc: fix 32-bit truncation in the vrealloc() grow-in-place check Artem Lytkin
2026-07-30 9:06 ` [PATCH v2 3/3] mm/vmalloc: make vm_struct.nr_pages an unsigned long Artem Lytkin
2026-07-30 13:04 ` [PATCH] " Uladzislau Rezki
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=20260730130923.9e71be5f477ee3db333cf0f8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=iprintercanon@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shivamkalra98@zohomail.in \
--cc=urezki@gmail.com \
--cc=willy@infradead.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