From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757263AbcAJPIr (ORCPT ); Sun, 10 Jan 2016 10:08:47 -0500 Received: from smtprelay0025.hostedemail.com ([216.40.44.25]:41511 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756833AbcAJPIp (ORCPT ); Sun, 10 Jan 2016 10:08:45 -0500 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: X-HE-Tag: sheet24_4bb96679f3906 X-Filterd-Recvd-Size: 3007 Message-ID: <1452438519.7773.23.camel@perches.com> Subject: Re: [PATCH v2 2/3] checkpatch: check for __smp outside barrier.h From: Joe Perches To: "Michael S. Tsirkin" , linux-kernel@vger.kernel.org Cc: Andy Whitcroft , Peter Zijlstra , Arnd Bergmann , linux-arch@vger.kernel.org, Andrew Cooper , virtualization@lists.linux-foundation.org, Stefano Stabellini , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , David Miller , linux-ia64@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, sparclinux@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-metag@vger.kernel.org, linux-mips@linux-mips.org, x86@kernel.org, user-mode-linux-devel@lists.sourceforge.net, adi-buildroot-devel@lists.sourceforge.net, linux-sh@vger.kernel.org, linux-xtensa@linux-xtensa.org, xen-devel@lists.xenproject.org, Ingo Molnar , Tony Lindgren , Andrey Konovalov , Russell King - ARM Linux Date: Sun, 10 Jan 2016 07:08:39 -0800 In-Reply-To: <1452427000-4520-3-git-send-email-mst@redhat.com> References: <1452427000-4520-1-git-send-email-mst@redhat.com> <1452427000-4520-3-git-send-email-mst@redhat.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.3-1ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2016-01-10 at 13:57 +0200, Michael S. Tsirkin wrote: > Introduction of __smp barriers cleans up a bunch of duplicate code, but > it gives people an additional handle onto a "new" set of barriers - just > because they're prefixed with __* unfortunately doesn't stop anyone from > using it (as happened with other arch stuff before.) > > Add a checkpatch test so it will trigger a warning. [] > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl [] > @@ -5141,6 +5141,16 @@ sub process { >   } >   } >   > + my $underscore_smp_barriers = qr{__smp_($smp_barriers)}x; another unnecessary capture group > + > + if ($realfile !~ m@^include/asm-generic/@ && > +     $realfile !~ m@/barrier\.h$@ && > +     $line =~ m/\b($underscore_smp_barriers)\s*\(/ && > +     $line !~ m/^.\s*\#\s*define\s+($underscore_smp_barriers)\s*\(/) { > + WARN("MEMORY_BARRIER", > +      "__smp memory barriers shouldn't be used outside barrier.h and asm-generic\n" . $herecurr); > + } > + >  # check for waitqueue_active without a comment. >   if ($line =~ /\bwaitqueue_active\s*\(/) { >   if (!ctx_has_comment($first_line, $linenr)) {