Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752009AbbGKXph (ORCPT ); Sat, 11 Jul 2015 19:45:37 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34504 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751809AbbGKXpg (ORCPT ); Sat, 11 Jul 2015 19:45:36 -0400 Date: Sun, 12 Jul 2015 01:43:58 +0200 From: Oleg Nesterov To: Andrew Morton Cc: Andy Lutomirski , Hugh Dickins , Kirill Shutemov , Linus Torvalds , Pavel Emelyanov , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/3] special_mapping_fault() is broken Message-ID: <20150711234358.GA958@redhat.com> References: <20150710165121.GA10341@redhat.com> <20150710145212.4440052265c4f6e074d1f391@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150710145212.4440052265c4f6e074d1f391@linux-foundation.org> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1661 Lines: 40 On 07/10, Andrew Morton wrote: > > On Fri, 10 Jul 2015 18:51:21 +0200 Oleg Nesterov wrote: > > > special_mapping_fault() is absolutely broken. It seems it was always > > wrong, but this didn't matter until vdso/vvar started to use more than > > one page. > > > > The patches are the same, just 1/3 was re-diffed on top of the recent > > 6b7339f4c31ad "mm: avoid setting up anonymous pages into file mapping" > > from Kirill. > > > > And after this change vma_is_anonymous() becomes really trivial, it > > simply checks vm_ops == NULL. However, I do think the helper makes > > sense. There are a lot of ->vm_ops != NULL checks, the helper makes > > the caller's code more understandable (self-documented) and this is > > more grep-friendly. > > I'm trying to work out which kernel version(s) this should go into, > without a lot of success. > > What do we think the worst-case effects of the bug? Ah, I should have mentioned this. And when I re-read my messages I see that "absolutely broken" looks like "should be fixed asap". Sorry for confusion. No, this bug is not serious. Nothing bad can happen from the kernel perspective. And I doubt that some application will ever unmap/remap the part of vdso or any other install_special_mapping() user. So this is just correctness fix. In fact, to me the main problem is that I was totally confused when I tried to read/understand this code ;) Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/