On Fri, 27 Jul 2018 06:41:56 -0700 Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > On Fri, Jul 27, 2018 at 09:48:17PM +1000, Nicholas Piggin wrote: > > The page table fragment allocator uses the main page refcount racily > > with respect to speculative references. A customer observed a BUG due > > to page table page refcount underflow in the fragment allocator. This > > can be caused by the fragment allocator set_page_count stomping on a > > speculative reference, and then the speculative failure handler > > decrements the new reference, and the underflow eventually pops when > > the page tables are freed. > > Oof. Can't you fix this instead by using page_ref_add() instead of > set_page_count()? It's ugly doing it that way. The problem is we have a page table destructor and that would be missed if the spec ref was the last put. In practice with RCU page table freeing maybe you can say there will be no spec ref there (unless something changes), but still it just seems much simpler doing this and avoiding any complexity or relying on other synchronization. > > > Any objection to the struct page change to grab the arch specific > > page table page word for powerpc to use? If not, then this should > > go via powerpc tree because it's inconsequential for core mm. > > I want (eventually) to get to the point where every struct page carries > a pointer to the struct mm that it belongs to. It's good for debugging > as well as handling memory errors in page tables. That doesn't seem like it should be a problem, there's some spare words there for arch independent users. Thanks, Nick
