Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932770Ab2EOANU (ORCPT ); Mon, 14 May 2012 20:13:20 -0400 Received: from na3sys009aog131.obsmtp.com ([74.125.149.247]:33239 "HELO na3sys009aog131.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S932710Ab2EOANT (ORCPT ); Mon, 14 May 2012 20:13:19 -0400 MIME-Version: 1.0 In-Reply-To: <1337034892.8512.652.camel@edumazet-glaptop> References: <1337034597-1826-1-git-send-email-pshelar@nicira.com> <1337034892.8512.652.camel@edumazet-glaptop> Date: Mon, 14 May 2012 17:13:17 -0700 Message-ID: Subject: Re: [PATCH v2] mm: Fix slab->page _count corruption. From: Pravin Shelar To: Eric Dumazet Cc: cl@linux.com, penberg@kernel.org, mpm@selenic.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, jesse@nicira.com, abhide@nicira.com Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1111 Lines: 26 On Mon, May 14, 2012 at 3:34 PM, Eric Dumazet wrote: > On Mon, 2012-05-14 at 15:29 -0700, Pravin B Shelar wrote: >> On arches that do not support this_cpu_cmpxchg_double slab_lock is used >> to do atomic cmpxchg() on double word which contains page->_count. >> page count can be changed from get_page() or put_page() without taking >> slab_lock. That corrupts page counter. >> >> Following patch fixes it by moving page->_count out of cmpxchg_double >> data. So that slub does no change it while updating slub meta-data in >> struct page. > > I say again : Page is owned by slub, so get_page() or put_page() is not > allowed ? > This is already done in multiple subsystem in Linux kernel. e.g. ocfs, xfs, etc. So object from slab can be passed to IO using DMA. I don't think this rule you referring to is enforced anywhere. Thanks, Pravin. -- 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/