From: Christoph Hellwig <hch@infradead.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Jerome Glisse <jglisse@redhat.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Leon Romanovsky <leonro@mellanox.com>,
Doug Ledford <dledford@redhat.com>,
Artemy Kovalyov <artemyko@mellanox.com>,
Moni Shoua <monis@mellanox.com>,
Mike Marciniszyn <mike.marciniszyn@intel.com>,
Kaike Wan <kaike.wan@intel.com>,
Dennis Dalessandro <dennis.dalessandro@intel.com>,
linux-mm@kvack.org, akpm@linux-foundation.org
Subject: Re: [PATCH v4 0/1] Use HMM for ODP v4
Date: Thu, 23 May 2019 23:40:51 -0700 [thread overview]
Message-ID: <20190524064051.GA28855@infradead.org> (raw)
In-Reply-To: <20190523191038.GG12159@ziepe.ca>
On Thu, May 23, 2019 at 04:10:38PM -0300, Jason Gunthorpe wrote:
>
> On Thu, May 23, 2019 at 02:24:58PM -0400, Jerome Glisse wrote:
> > I can not take mmap_sem in range_register, the READ_ONCE is fine and
> > they are no race as we do take a reference on the hmm struct thus
>
> Of course there are use after free races with a READ_ONCE scheme, I
> shouldn't have to explain this.
>
> If you cannot take the read mmap sem (why not?), then please use my
> version and push the update to the driver through -mm..
I think it would really help if we queue up these changes in a git tree
that can be pulled into the driver trees. Given that you've been
doing so much work to actually make it usable I'd nominate rdma for the
"lead" tree.
next prev parent reply other threads:[~2019-05-24 6:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190411181314.19465-1-jglisse@redhat.com>
[not found] ` <20190506195657.GA30261@ziepe.ca>
[not found] ` <20190521205321.GC3331@redhat.com>
[not found] ` <20190522005225.GA30819@ziepe.ca>
[not found] ` <20190522174852.GA23038@redhat.com>
2019-05-22 19:22 ` Jason Gunthorpe
2019-05-22 21:49 ` Jerome Glisse
2019-05-22 22:43 ` Jason Gunthorpe
2019-05-22 20:12 ` Jason Gunthorpe
2019-05-22 21:12 ` Ralph Campbell
2019-05-22 22:06 ` Jerome Glisse
2019-05-22 22:04 ` Jerome Glisse
2019-05-22 22:39 ` Jason Gunthorpe
2019-05-22 22:42 ` Jerome Glisse
2019-05-22 22:52 ` Jason Gunthorpe
[not found] ` <20190522235737.GD15389@ziepe.ca>
[not found] ` <20190523150432.GA5104@redhat.com>
[not found] ` <20190523154149.GB12159@ziepe.ca>
[not found] ` <20190523155207.GC5104@redhat.com>
[not found] ` <20190523163429.GC12159@ziepe.ca>
[not found] ` <20190523173302.GD5104@redhat.com>
[not found] ` <20190523175546.GE12159@ziepe.ca>
[not found] ` <20190523182458.GA3571@redhat.com>
[not found] ` <20190523191038.GG12159@ziepe.ca>
2019-05-24 6:40 ` Christoph Hellwig [this message]
2019-05-24 12:44 ` RFC: Run a dedicated hmm.git for 5.3 Jason Gunthorpe
2019-05-24 16:27 ` Daniel Vetter
2019-05-24 16:53 ` Jason Gunthorpe
2019-05-24 16:59 ` Daniel Vetter
2019-05-25 22:52 ` Andrew Morton
2019-05-27 19:12 ` Jason Gunthorpe
2019-06-06 15:25 ` Jason Gunthorpe
2019-06-06 19:53 ` Stephen Rothwell
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=20190524064051.GA28855@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=artemyko@mellanox.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jglisse@redhat.com \
--cc=kaike.wan@intel.com \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=monis@mellanox.com \
/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