linux-kernel - [RESENT] kernel-doc: unable to parse DECLARE

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>] [day] [month] [year] [list]

Message-ID: <trinity-e14a1ae1-7b8b-40ca-8af7-74729722e934-1446396806691@3capp-webde-bap36>
Date:	Sun, 1 Nov 2015 17:53:26 +0100
From:	conchur@....de
To:	linux-kernel@...r.kernel.org
Cc:	"Jonathan Corbet" <corbet@....net>,
	"Ben Hutchings" <ben@...adent.org.uk>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Randy Dunlap" <rdunlap@...radead.org>,
	"Danilo Cesar Lemes de Paula" <danilo.cesar@...labora.co.uk>,
	"Jérémy Bobbio" <lunar@...ian.org>,
	"Johannes Berg" <johannes.berg@...el.com>,
	"Bart Van Assche" <bart.vanassche@...disk.com>
Subject: [RESENT] kernel-doc: unable to parse DECLARE_BITMAP in structs

(resent because vger.kernel.org rejected the mail)

Hi,
 
just noticed that kernel-doc is not able to parse members declared with DECLARED_BITMAP inside a struct. Here is my patch:
 
--- a/scripts/kernel-doc
+++ b/scripts/kernel-doc
@@ -1802,6 +1802,8 @@ sub dump_struct($$) {
 	$members =~ s/__attribute__\s*\(\([a-z,_\*\s\(\)]*\)\)//i;
 	$members =~ s/__aligned\s*\([^;]*\)//gos;
 	$members =~ s/\s*CRYPTO_MINALIGN_ATTR//gos;
+	# replace DECLARE_BITMAP
+	$members =~ s/DECLARE_BITMAP\s*\(([^,)]+), ([^,)]+)\)/unsigned long $1\[BITS_TO_LONGS($2)\]/gos;
 
 	create_parameterlist($members, ';', $file);
 	check_sections($file, $declaration_name, "struct", $sectcheck, $struct_actual, $nested);
--
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/