From: Jason Gunthorpe <jgg@nvidia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
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 22:54:34 -0400 [thread overview]
Message-ID: <20251206025434.GA1422789@nvidia.com> (raw)
In-Reply-To: <CAHk-=wj1aw7p-JkWdcJOkQQ279qgppG7_1kxFQAqaak7fEQAjw@mail.gmail.com>
On Fri, Dec 05, 2025 at 01:56:17PM -0800, Linus Torvalds wrote:
> On Wed, 3 Dec 2025 at 21:29, Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > Ankit Agrawal:
> > vfio/nvgrace-gpu: register device memory for poison handling
>
> So I had to look at this one because there was a conflict ("int ret"
> had been removed by another commit), and after looking at it I ended
> up deciding to revert this patch entirely.
>
> I may be wrong, but that patch looks *COMPETELY* broken.
You are right, it is security broken, it worked functionally in
testing because it used qemu which only mmaps once. mmaping twice will
corrupt an interval tree.
Alex and I also noticed it this week also when we were looking at the
same conflcit. We also found another serious bug in how it uses pgoff
that renders it functionally broken after merging all the branches
together as the merge'd tree also changes how pgoff worked. :\
Ankit has been working on a fix this week and we planned to send you a
fix/revert in the next week, travel permitting and so on.
> Again - maybe I'm missing something. If so, that commit can be re-done
> with explanations of why it's all correct.
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.
Regards,
Jason
next prev parent reply other threads:[~2025-12-06 2:54 UTC|newest]
Thread overview: 8+ 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 [this message]
2025-12-06 3:43 ` Linus Torvalds
2025-12-05 22:14 ` pr-tracker-bot
2025-12-11 11:12 ` Daniel Palmer
2025-12-11 22:59 ` Joshua Hahn
2025-12-12 1:53 ` Joshua Hahn
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=20251206025434.GA1422789@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex@shazbot.org \
--cc=ankita@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mm-commits@vger.kernel.org \
--cc=torvalds@linux-foundation.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®