From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763194AbbA3VmT (ORCPT ); Fri, 30 Jan 2015 16:42:19 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:47208 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756264AbbA3VmS (ORCPT ); Fri, 30 Jan 2015 16:42:18 -0500 Date: Fri, 30 Jan 2015 13:42:17 -0800 From: Andrew Morton To: Andrey Ryabinin Cc: linux-kernel@vger.kernel.org, Dmitry Vyukov , Konstantin Serebryany , Dmitry Chernenkov , Andrey Konovalov , Yuri Gribov , Konstantin Khlebnikov , Sasha Levin , Christoph Lameter , Joonsoo Kim , Dave Hansen , Andi Kleen , x86@kernel.org, linux-mm@kvack.org, Pekka Enberg , David Rientjes Subject: Re: [PATCH v10 06/17] mm: slub: introduce metadata_access_enable()/metadata_access_disable() Message-Id: <20150130134217.73d6f43f8257936275351834@linux-foundation.org> In-Reply-To: <54CBB9C9.3060500@samsung.com> References: <1404905415-9046-1-git-send-email-a.ryabinin@samsung.com> <1422544321-24232-1-git-send-email-a.ryabinin@samsung.com> <1422544321-24232-7-git-send-email-a.ryabinin@samsung.com> <20150129151243.fd76aca21757b1ca5b62163e@linux-foundation.org> <54CBB9C9.3060500@samsung.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 30 Jan 2015 20:05:13 +0300 Andrey Ryabinin wrote: > >> --- a/mm/slub.c > >> +++ b/mm/slub.c > >> @@ -467,13 +467,23 @@ static int slub_debug; > >> static char *slub_debug_slabs; > >> static int disable_higher_order_debug; > >> > >> +static inline void metadata_access_enable(void) > >> +{ > >> +} > >> + > >> +static inline void metadata_access_disable(void) > >> +{ > >> +} > > > > Some code comments here would be useful. What they do, why they exist, > > etc. The next patch fills them in with > > kasan_disable_local/kasan_enable_local but that doesn't help the reader > > to understand what's going on. The fact that > > kasan_disable_local/kasan_enable_local are also undocumented doesn't > > help. > > > > Ok, How about this? > > /* > * This hooks separate payload access from metadata access. > * Useful for memory checkers that have to know when slub > * accesses metadata. > */ "These hooks". I still don't understand :( Maybe I'm having a more-stupid-than-usual day. How can a function "separate access"? What does this mean? More details, please. I think I've only once seen a comment which had too much info!