linux-kernel - Re: [PATCH] checkpatch: teach checkpatch about rcu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1290100547.2781.206.camel@edumazet-laptop>
Date:	Thu, 18 Nov 2010 18:15:47 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	"Michael S. Tsirkin" <mst@...hat.com>
Cc:	Andy Whitcroft <apw@...onical.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Joe Perches <joe@...ches.com>,
	Patrick Pannuto <ppannuto@...eaurora.org>,
	Wolfram Sang <w.sang@...gutronix.de>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] checkpatch: teach checkpatch about rcu

Le jeudi 18 novembre 2010 à 19:05 +0200, Michael S. Tsirkin a écrit :
> I got this:
> +       struct kvm_kernel_irq_routing_entry __rcu *irq_entry;
> which is because checkpatch does not know about __rcu.
> So here's a patch to teach it about that tag.
> 
> Signed-off-by: Michael S. Tsirkin <mst@...hat.com>
> ---
>  scripts/checkpatch.pl |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 2039acd..1b11c8e 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -143,6 +143,7 @@ our $Sparse	= qr{
>  			__must_check|
>  			__init_refok|
>  			__kprobes|
> +			__rcu|
>  			__ref
>  		}x;
>  


Hmm, why __percpu is in $Attribute, and __rcu in $Sparse ?



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/