From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io1-f71.google.com (mail-io1-f71.google.com [209.85.166.71]) by kanga.kvack.org (Postfix) with ESMTP id CD38D8E0002 for ; Mon, 14 Jan 2019 17:25:40 -0500 (EST) Received: by mail-io1-f71.google.com with SMTP id q18so495549ioj.5 for ; Mon, 14 Jan 2019 14:25:40 -0800 (PST) Received: from userp2130.oracle.com (userp2130.oracle.com. [156.151.31.86]) by mx.google.com with ESMTPS id e190si938870jac.117.2019.01.14.14.25.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Jan 2019 14:25:39 -0800 (PST) Date: Mon, 14 Jan 2019 14:25:29 -0800 From: Daniel Jordan Subject: Re: [PATCH] mm, swap: Potential NULL dereference in get_swap_page_of_type() Message-ID: <20190114222529.43zay6r242ipw5jb@ca-dmjordan1.us.oracle.com> References: <20190111095919.GA1757@kadam> <20190111174128.oak64htbntvp7j6y@ca-dmjordan1.us.oracle.com> <20190111232007.GA27982@andrea> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190111232007.GA27982@andrea> Sender: owner-linux-mm@kvack.org List-ID: To: Andrea Parri Cc: Daniel Jordan , Dan Carpenter , Andrew Morton , Shaohua Li , Huang Ying , Dave Hansen , Stephen Rothwell , Omar Sandoval , Tejun Heo , Andi Kleen , linux-mm@kvack.org, kernel-janitors@vger.kernel.org, "Paul E. McKenney" , Alan Stern , Peter Zijlstra , Will Deacon On Sat, Jan 12, 2019 at 12:20:07AM +0100, Andrea Parri wrote: > On Fri, Jan 11, 2019 at 09:41:28AM -0800, Daniel Jordan wrote: > > On Fri, Jan 11, 2019 at 12:59:19PM +0300, Dan Carpenter wrote: > > > diff --git a/mm/swapfile.c b/mm/swapfile.c > > > index f0edf7244256..21e92c757205 100644 > > > --- a/mm/swapfile.c > > > +++ b/mm/swapfile.c > > > @@ -1048,9 +1048,12 @@ swp_entry_t get_swap_page_of_type(int type) > > > struct swap_info_struct *si; > > > pgoff_t offset; > > > > > > + if (type >= nr_swapfiles) > > > + goto fail; > > > + > > > > As long as we're worrying about NULL, I think there should be an smp_rmb here > > to ensure swap_info[type] isn't NULL in case of an (admittedly unlikely) racing > > swapon that increments nr_swapfiles. See smp_wmb in alloc_swap_info and the > > matching smp_rmb's in the file. And READ_ONCE's on either side of the barrier > > per LKMM. > > > > I'm adding Andrea (randomly selected from the many LKMM folks to avoid spamming > > all) who can correct me if I'm wrong about any of this. > > This is to confirm that your analysis seems correct to me: the barriers > should guarantee that get_swap_page_of_type() will observe the store to > swap_info[type] performed by alloc_swap_info() (or a "co"-later store), > provided get_swap_page_of_type() observes the increment of nr_swapfiles > performed by the (same instance of) alloc_swap_info(). That's good to hear, thanks for looking into it. > One clarification about the READ_ONCE() matter: the LKMM cannot handle > plain or unmarked (shared memory) accesses in their generality at the > moment (patches providing support for these accesses are in the making, > but they will take some time); IAC, I'm confident to anticipate that, > for the particular pattern in question (aka, MP), marking the accesses > to nr_swapfiles will be "LKMM-sane" (one way to achieve this would be > to convert nr_swapfiles to an atomic_t type...). I guess you mean we could either use READ_ONCE or make nr_swapfiles atomic, they're different ways of achieving the same thing. > I take the liberty of adding other LKMM folks (so that they can blame > me for "the spam"! ;-) ): I've learnt from experience that four or more > eyes are better than two when it comes to discuss these matters... ;-) Ok, it's fine with me as long as they blame you :) > > > si = swap_info[type];