On Fri, Sep 28, 2018 at 12:06:12PM -0700, John Hubbard wrote: > On 9/28/18 8:29 AM, Jerome Glisse wrote: > > On Thu, Sep 27, 2018 at 10:39:45PM -0700, john.hubbard@xxxxxxxxx wrote: > >> From: John Hubbard <jhubbard@xxxxxxxxxx> > >> > >> Hi, > >> > >> This short series prepares for eventually fixing the problem described > >> in [1], and is following a plan listed in [2]. > >> > >> I'd like to get the first two patches into the -mm tree. > >> > >> Patch 1, although not technically critical to do now, is still nice to have, > >> because it's already been reviewed by Jan, and it's just one more thing on the > >> long TODO list here, that is ready to be checked off. > >> > >> Patch 2 is required in order to allow me (and others, if I'm lucky) to start > >> submitting changes to convert all of the callsites of get_user_pages*() and > >> put_page(). I think this will work a lot better than trying to maintain a > >> massive patchset and submitting all at once. > >> > >> Patch 3 converts infiniband drivers: put_page() --> put_user_page(). I picked > >> a fairly small and easy example. > >> > >> Patch 4 converts a small driver from put_page() --> release_user_pages(). This > >> could just as easily have been done as a change from put_page() to > >> put_user_page(). The reason I did it this way is that this provides a small and > >> simple caller of the new release_user_pages() routine. I wanted both of the > >> new routines, even though just placeholders, to have callers. > >> > >> Once these are all in, then the floodgates can open up to convert the large > >> number of get_user_pages*() callsites. > >> > >> [1] https://lwn.net/Articles/753027/ : "The Trouble with get_user_pages()" > >> > >> [2] https://lkml.kernel.org/r/20180709080554.21931-1-jhubbard@xxxxxxxxxx > >> Proposed steps for fixing get_user_pages() + DMA problems. > >> > > > > So the solution is to wait (possibly for days, months, years) that the > > RDMA or GPU which did GUP and do not have mmu notifier, release the page > > (or put_user_page()) ? > > > > This sounds bads. Like i said during LSF/MM there is no way to properly > > fix hardware that can not be preempted/invalidated ... most GPU are fine. > > Few RDMA are fine, most can not ... > > > > Hi Jerome, > > Personally, I'm think that this particular design is the best one I've seen > so far, but if other, better designs show up, than let's do those instead, sure. > > I guess your main concern is that this might take longer than other approaches. > > As for time frame, perhaps I made it sound worse than it really is. I have patches > staged already for all of the simpler call sites, and for about half of the more > complicated ones. The core solution in mm is not large, and we've gone through a > few discussion threads about it back in July or so, so it shouldn't take too long > to perfect it. > > So it may be a few months to get it all reviewed and submitted, but I don't > see "years" by any stretch. Bit of miss-comprehention there :) By month, years, i am talking about the time it will take for some user to release the pin they have on the page. Not the time to push something upstream. AFAICT RDMA driver do not have any upper bound on how long they can hold a page reference and thus your solution can leave one CPU core stuck for as long as the pin is active. Worst case might lead to all CPU core waiting for something that might never happen. > > > > If it is just about fixing the set_page_dirty() bug then just looking at > > refcount versus mapcount should already tell you if you can remove the > > buffer head from the page or not. Which would fix the bug without complex > > changes (i still like the put_user_page just for symetry with GUP). > > > > It's about more than that. The goal is to make it safe and correct to > use a non-CPU device to read and write to "pinned" memory, especially when > that memory is backed by a file system. > > I recall there were objections to just narrowly fixing the set_page_dirty() > bug, because the underlying problem is large and serious. So here we are. Except that you can not solve that issue without proper hardware. GPU are fine. RDMA are broken except the mellanox5 hardware which can invalidate at anytime its page table thus allowing to write protect the page at any time. With the solution put forward here you can potentialy wait _forever_ for the driver that holds a pin to drop it. This was the point i was trying to get accross during LSF/MM. You can not fix broken hardware that decided to use GUP to do a feature they can't reliably do because their hardware is not capable to behave. Because code is easier here is what i was meaning: https://cgit.freedesktop.org/~glisse/linux/commit/?h=gup&id=a5dbc0fe7e71d347067579f13579df372ec48389 https://cgit.freedesktop.org/~glisse/linux/commit/?h=gup&id=01677bc039c791a16d5f82b3ef84917d62fac826 Cheers, Jérôme
