Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753633Ab3HVGlr (ORCPT ); Thu, 22 Aug 2013 02:41:47 -0400 Received: from relay.parallels.com ([195.214.232.42]:34101 "EHLO relay.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753396Ab3HVGlp (ORCPT ); Thu, 22 Aug 2013 02:41:45 -0400 Message-ID: <5215B2A2.6090705@parallels.com> Date: Thu, 22 Aug 2013 10:41:38 +0400 From: Pavel Emelyanov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: Dave Jones , Cyrill Gorcunov CC: Linus Torvalds , "H. Peter Anvin" , David Vrabel , Jan Beulich , Andy Lutomirski , Andrew Morton , , Boris Ostrovsky , Konrad Rzeszutek Wilk , Ingo Molnar , "linux-kernel@vger.kernel.org" , Subject: Re: Regression: x86/mm: new _PTE_SWP_SOFT_DIRTY bit conflicts with existing use References: <5214F09002000078000ED5C3@nat28.tlf.novell.com> <20130821154238.GV18673@moon> <521500E102000078000ED65C@nat28.tlf.novell.com> <20130821161946.GW18673@moon> <5214F128.1000901@citrix.com> <20130821172547.GY18673@moon> <20130821181733.GC3814@moon> <4fec3e5b-695c-438b-ad6d-55ca50becc4c@email.android.com> <20130821190307.GB18673@moon> <20130822005115.GA1188@redhat.com> In-Reply-To: <20130822005115.GA1188@redhat.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Originating-IP: [89.169.95.100] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1385 Lines: 35 On 08/22/2013 04:51 AM, Dave Jones wrote: > On Wed, Aug 21, 2013 at 04:04:54PM -0700, Linus Torvalds wrote: > > On Wed, Aug 21, 2013 at 12:03 PM, Cyrill Gorcunov wrote: > > > > > > I personally don't see bug here because > > > > > > - this swapped page soft dirty bit is set for non-present entries only, > > > never for present ones, just at moment we form swap pte entry > > > > > > - i don't find any code which would test for this bit directly without > > > is_swap_pte call > > > > Ok, having gone through the places that use swp_*soft_dirty(), I have > > to agree. Afaik, it's only ever used on a swap-entry that has (by > > definition) the P bit clear. So with or without Xen, I don't see how > > it can make any difference. > > > > David/Konrad - did you actually see any issues, or was this just from > > (mis)reading the code? > > Could this explain what I'm seeing in another thread ? > https://lkml.org/lkml/2013/8/7/27 Was it caught with CONFIG_MEM_SOFT_DIRTY on or off? In the latter case all new bits manipulations are no-op and couldn't cause this. > Dave Thanks, Pavel -- 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/