linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ankit Agrawal <ankita@nvidia.com>,
	 Alex Williamson <alex@shazbot.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 mm-commits@vger.kernel.org
Subject: Re: [GIT PULL] MM updates for 6.19-rc1
Date: Fri, 5 Dec 2025 19:43:52 -0800	[thread overview]
Message-ID: <CAHk-=wj681NMt4ofHWVDzbcb2CjyAZWnVYX=9eJ5tmYjEONNBA@mail.gmail.com> (raw)
In-Reply-To: <20251206025434.GA1422789@nvidia.com>

On Fri, 5 Dec 2025 at 18:54, Jason Gunthorpe <jgg@nvidia.com> wrote:
>
> Reverting it now works well enough too. Let's see if Ankit can prepare
> a new revision and perhaps Alex can forward it next week or very early
> rc1 after LPC.

So adding that memory poisoning logic at mmap time looks crazy to me.
The mmap has *nothing* to do with memory poisoning. The memory is
there whether it is mapped or not, and admittedly it's harder to
_access_ when not mapped, but it still has nothing to do with mmap.

As far as I can tell, that memory poisoning logic should be
added/removed when the device is registered or unregistered, and there
is nothing about mmap that should have any effect what-so-ever.

                     Linus


  reply	other threads:[~2025-12-06  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  5:29 Andrew Morton
2025-12-05 21:56 ` Linus Torvalds
2025-12-06  2:54   ` Jason Gunthorpe
2025-12-06  3:43     ` Linus Torvalds [this message]
2025-12-05 22:14 ` pr-tracker-bot

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='CAHk-=wj681NMt4ofHWVDzbcb2CjyAZWnVYX=9eJ5tmYjEONNBA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex@shazbot.org \
    --cc=ankita@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.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