From: Vlastimil Babka <vbabka@suse.cz> To: "Kirill A. Shutemov" <kirill@shutemov.name>, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> Cc: Andrew Morton <akpm@linux-foundation.org>, "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>, Hugh Dickins <hughd@google.com>, Andrea Arcangeli <aarcange@redhat.com>, Dave Hansen <dave.hansen@intel.com>, Johannes Weiner <hannes@cmpxchg.org>, Michal Hocko <mhocko@suse.cz>, David Rientjes <rientjes@google.com>, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Christoph Lameter <cl@linux.com> Subject: Re: [PATCHv3 4/5] mm: make compound_head() robust Date: Wed, 26 Aug 2015 17:39:13 +0200 [thread overview] Message-ID: <55DDDDA1.4090407@suse.cz> (raw) In-Reply-To: <20150826150412.GA16412@node.dhcp.inet.fi> On 08/26/2015 05:04 PM, Kirill A. Shutemov wrote: >>> That's >>> bad news then. It's not that we would trigger that bit when the rcu_head part of >>> the union is "active". It's that pfn scanners could inspect such page at >>> arbitrary time, see the bit 0 set (due to RCU processing) and think that it's a >>> tail page of a compound page, and interpret the rest of the pointer as a pointer >>> to the head page (to test it for flags etc). >> >> On the other hand, if you avoid scanning rcu_head structures for pages >> that are currently waiting for a grace period, no problem. RCU does >> not use the rcu_head structure at all except for during the time between >> when call_rcu() is invoked on that rcu_head structure and the time that >> the callback is invoked. >> >> Is there some other page state that indicates that the page is waiting >> for a grace period? If so, you could simply avoid testing that bit in >> that case. > > No, I don't think so. > > For compound pages most of info of its state is stored in head page (e.g. > page_count(), flags, etc). So if we examine random page (pfn scanner case) > the very first thing we want to know if we stepped on tail page. > PageTail() is what I wanted to encode in the bit... > > What if we change order of fields within rcu_head and put ->func first? Or change the order of compound_head wrt the rest? > Can we expect this pointer to have bit 0 always clear? That's probably a question whether $compiler is guaranteed to align functions on all architectures...
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz> To: "Kirill A. Shutemov" <kirill@shutemov.name>, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> Cc: Andrew Morton <akpm@linux-foundation.org>, "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>, Hugh Dickins <hughd@google.com>, Andrea Arcangeli <aarcange@redhat.com>, Dave Hansen <dave.hansen@intel.com>, Johannes Weiner <hannes@cmpxchg.org>, Michal Hocko <mhocko@suse.cz>, David Rientjes <rientjes@google.com>, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Christoph Lameter <cl@linux.com> Subject: Re: [PATCHv3 4/5] mm: make compound_head() robust Date: Wed, 26 Aug 2015 17:39:13 +0200 [thread overview] Message-ID: <55DDDDA1.4090407@suse.cz> (raw) In-Reply-To: <20150826150412.GA16412@node.dhcp.inet.fi> On 08/26/2015 05:04 PM, Kirill A. Shutemov wrote: >>> That's >>> bad news then. It's not that we would trigger that bit when the rcu_head part of >>> the union is "active". It's that pfn scanners could inspect such page at >>> arbitrary time, see the bit 0 set (due to RCU processing) and think that it's a >>> tail page of a compound page, and interpret the rest of the pointer as a pointer >>> to the head page (to test it for flags etc). >> >> On the other hand, if you avoid scanning rcu_head structures for pages >> that are currently waiting for a grace period, no problem. RCU does >> not use the rcu_head structure at all except for during the time between >> when call_rcu() is invoked on that rcu_head structure and the time that >> the callback is invoked. >> >> Is there some other page state that indicates that the page is waiting >> for a grace period? If so, you could simply avoid testing that bit in >> that case. > > No, I don't think so. > > For compound pages most of info of its state is stored in head page (e.g. > page_count(), flags, etc). So if we examine random page (pfn scanner case) > the very first thing we want to know if we stepped on tail page. > PageTail() is what I wanted to encode in the bit... > > What if we change order of fields within rcu_head and put ->func first? Or change the order of compound_head wrt the rest? > Can we expect this pointer to have bit 0 always clear? That's probably a question whether $compiler is guaranteed to align functions on all architectures... -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-08-26 15:39 UTC|newest] Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-19 9:21 [PATCHv3 0/5] Fix compound_head() race Kirill A. Shutemov 2015-08-19 9:21 ` Kirill A. Shutemov 2015-08-19 9:21 ` [PATCHv3 1/5] mm: drop page->slab_page Kirill A. Shutemov 2015-08-19 9:21 ` Kirill A. Shutemov 2015-08-24 14:59 ` Vlastimil Babka 2015-08-24 14:59 ` Vlastimil Babka 2015-08-24 15:02 ` Vlastimil Babka 2015-08-24 15:02 ` Vlastimil Babka 2015-08-25 17:24 ` Kirill A. Shutemov 2015-08-25 17:24 ` Kirill A. Shutemov 2015-08-19 9:21 ` [PATCHv3 2/5] zsmalloc: use page->private instead of page->first_page Kirill A. Shutemov 2015-08-19 9:21 ` Kirill A. Shutemov 2015-08-24 15:04 ` Vlastimil Babka 2015-08-24 15:04 ` Vlastimil Babka 2015-08-19 9:21 ` [PATCHv3 3/5] mm: pack compound_dtor and compound_order into one word in struct page Kirill A. Shutemov 2015-08-19 9:21 ` Kirill A. Shutemov 2015-08-20 23:26 ` Andrew Morton 2015-08-20 23:26 ` Andrew Morton 2015-08-21 7:13 ` Michal Hocko 2015-08-21 7:13 ` Michal Hocko 2015-08-21 10:40 ` Kirill A. Shutemov 2015-08-21 10:40 ` Kirill A. Shutemov 2015-08-21 10:51 ` Michal Hocko 2015-08-21 10:51 ` Michal Hocko 2015-08-19 9:21 ` [PATCHv3 4/5] mm: make compound_head() robust Kirill A. Shutemov 2015-08-19 9:21 ` Kirill A. Shutemov 2015-08-20 23:36 ` Andrew Morton 2015-08-20 23:36 ` Andrew Morton 2015-08-21 12:10 ` Kirill A. Shutemov 2015-08-21 12:10 ` Kirill A. Shutemov 2015-08-21 16:11 ` Christoph Lameter 2015-08-21 16:11 ` Christoph Lameter 2015-08-21 19:31 ` Kirill A. Shutemov 2015-08-21 19:31 ` Kirill A. Shutemov 2015-08-21 19:34 ` Andrew Morton 2015-08-21 19:34 ` Andrew Morton 2015-08-21 21:15 ` Christoph Lameter 2015-08-21 21:15 ` Christoph Lameter 2015-08-24 15:49 ` Vlastimil Babka 2015-08-24 15:49 ` Vlastimil Babka 2015-08-25 11:44 ` Vlastimil Babka 2015-08-25 11:44 ` Vlastimil Babka 2015-08-25 18:33 ` Kirill A. Shutemov 2015-08-25 18:33 ` Kirill A. Shutemov 2015-08-25 20:11 ` Paul E. McKenney 2015-08-25 20:11 ` Paul E. McKenney 2015-08-25 20:46 ` Vlastimil Babka 2015-08-25 20:46 ` Vlastimil Babka 2015-08-25 21:19 ` Paul E. McKenney 2015-08-25 21:19 ` Paul E. McKenney 2015-08-26 15:04 ` Kirill A. Shutemov 2015-08-26 15:04 ` Kirill A. Shutemov 2015-08-26 15:39 ` Vlastimil Babka [this message] 2015-08-26 15:39 ` Vlastimil Babka 2015-08-26 16:38 ` Paul E. McKenney 2015-08-26 16:38 ` Paul E. McKenney 2015-08-26 18:18 ` Hugh Dickins 2015-08-26 18:18 ` Hugh Dickins 2015-08-26 21:29 ` Paul E. McKenney 2015-08-26 21:29 ` Paul E. McKenney 2015-08-26 22:28 ` Hugh Dickins 2015-08-26 22:28 ` Hugh Dickins 2015-08-26 23:34 ` Paul E. McKenney 2015-08-26 23:34 ` Paul E. McKenney 2015-08-27 15:09 ` Michal Hocko 2015-08-27 15:09 ` Michal Hocko 2015-08-27 16:03 ` Michal Hocko 2015-08-27 16:03 ` Michal Hocko 2015-08-27 17:28 ` Hugh Dickins 2015-08-27 17:28 ` Hugh Dickins 2015-08-27 18:06 ` Michal Hocko 2015-08-27 18:06 ` Michal Hocko 2015-08-27 16:36 ` Paul E. McKenney 2015-08-27 16:36 ` Paul E. McKenney 2015-08-27 18:14 ` Michal Hocko 2015-08-27 18:14 ` Michal Hocko 2015-08-27 19:01 ` Paul E. McKenney 2015-08-27 19:01 ` Paul E. McKenney 2015-08-23 23:59 ` Jesper Dangaard Brouer 2015-08-23 23:59 ` Jesper Dangaard Brouer 2015-08-24 9:29 ` Kirill A. Shutemov 2015-08-24 9:29 ` Kirill A. Shutemov 2015-08-24 10:17 ` Kirill A. Shutemov 2015-08-24 10:17 ` Kirill A. Shutemov 2015-08-19 9:21 ` [PATCHv3 5/5] mm: use 'unsigned int' for page order Kirill A. Shutemov 2015-08-19 9:21 ` Kirill A. Shutemov 2015-08-20 8:32 ` Michal Hocko 2015-08-20 8:32 ` Michal Hocko 2015-08-20 12:31 ` [PATCHv3 0/5] Fix compound_head() race Kirill A. Shutemov 2015-08-20 12:31 ` Kirill A. Shutemov 2015-08-20 23:38 ` Andrew Morton 2015-08-20 23:38 ` Andrew Morton 2015-08-22 20:13 ` Hugh Dickins 2015-08-22 20:13 ` Hugh Dickins 2015-08-24 9:36 ` Kirill A. Shutemov 2015-08-24 9:36 ` Kirill A. Shutemov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=55DDDDA1.4090407@suse.cz \ --to=vbabka@suse.cz \ --cc=aarcange@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=cl@linux.com \ --cc=dave.hansen@intel.com \ --cc=hannes@cmpxchg.org \ --cc=hughd@google.com \ --cc=kirill.shutemov@linux.intel.com \ --cc=kirill@shutemov.name \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@suse.cz \ --cc=paulmck@linux.vnet.ibm.com \ --cc=rientjes@google.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.