mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stian Halseth <stian@itx.no>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Suren Baghdasaryan <surenb@google.com>
Cc: "Liam R. Howlett" <liam@infradead.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	 Vlastimil Babka <vbabka@kernel.org>,
	Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>,
	Andreas Larsson <andreas@gaisler.com>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	 sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] fs/proc/task_mmu: fix lost maps entries above 2^63
Date: Tue, 13 Oct 2026 17:03:12 +0200	[thread overview]
Message-ID: <662b749c05634b6990d072cb87a442687b41be33.camel@itx.no> (raw)
In-Reply-To: <e300f046-dcae-4539-bf89-92eb8c575e25@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

On Tue, 2026-10-13 at 16:40 +0200, David Hildenbrand (Arm) wrote:
> 
> Would it be cleaner to reject any special values, that is,
> SENTINEL_VMA_END and
> SENTINEL_VMA_GATE?
> 
> That would match the comment and the previous code idea: exclude only
> 0 and
> sentinels.
> 
> Could consider a simple addr_is_sentinel() helper.
> 
Agreed, that reads better. SENTINEL_VMA_END never gets this far, since
m_start() returns early for it, so it is no functional change. 

I'll send a v2 now, and maybe Suren can have a look directly at that
version.

Thanks,
Stian


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-10-13 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-11 16:20 Stian Halseth
2026-10-13 14:40 ` David Hildenbrand (Arm)
2026-10-13 15:03   ` Stian Halseth [this message]
2026-10-13 15:03   ` Lorenzo Stoakes (ARM)

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=662b749c05634b6990d072cb87a442687b41be33.camel@itx.no \
    --to=stian@itx.no \
    --cc=akpm@linux-foundation.org \
    --cc=andreas@gaisler.com \
    --cc=david@kernel.org \
    --cc=jannh@google.com \
    --cc=liam@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=pfalcato@suse.de \
    --cc=sparclinux@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.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
all inboxes | Powered by JetHome®