From: "André Almeida" <andrealmeid@collabora.com>
To: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: corbet@lwn.net, kernel@collabora.com,
"André Almeida" <andrealmeid@collabora.com>
Subject: [PATCH 0/2] kernel-doc: fix bug and improve dump_struct
Date: Tue, 17 Sep 2019 16:41:44 -0300 [thread overview]
Message-ID: <20190917194146.35642-1-andrealmeid@collabora.com> (raw)
Hello,
This patch series improves kernel-doc script at dump_struct()
subroutine by solving a bug and by making the parser more complete.
The current way that scripts/kernel-doc dump structs do not work for
nested structs with attributes (e.g. __packed) and without type alias
(e.g } alias1;). This is due to the way nested structs members are parsed.
Inside dump_struct(), the regex removes attributes and it surrounds
whitespaces. After that, it will do a foreach(id) loop for each alias.
However, we will have an empty string, and then the split function will
return nothing and the foreach will not have any iteration. The code will
then jump the loop and the substitution will fail since $newmember
is uninitialized.
This bug does not happen when the nested struct has no alias and no
attribute, since at process_proto_type() a whitespace is inserted in
order to ensure that the split will not fail. However, with any
attribute, this whitespace will be removed.
This patch solves this by replacing attributes with one whitespace, to
ensure that will have at least one whitespace.
Besides solving this bug at patch 1, I also add support for the
____cacheline_aligned_in_smp atribute at patch 2.
For testing and reproducing, create a file `code.h`:
/**
* struct foobar - description
* @number0: desc0
* @number1: desc1
* @number2: desc2
*/
struct foo {
int number0;
struct {
int number1;
} __packed;
struct {
int number2;
};
};
I've tested with CRYPTO_MINALIGN_ATTR, __attribute__((__aligned__(8)))
and __aligned() as well. Now, run the `./script/kernel-doc code.h`,
and this is the output:
Use of uninitialized value $newmember in substitution (s///) at
./scripts/kernel-doc line 1152, <IN> line 18.
.. c:type:: struct foo
description
**Definition**
::
struct foo {
int number0;
struct {
int number1;
};
struct {
int number2;
};
};
**Members**
``number0``
desc0
``{unnamed_struct}``
anonymous
``number2``
desc2
The output will not display the member number1 and will also display an
uninitialized warning. Running after the patch will get rid of the
warning and also display the description for number1:
[...]
**Members**
``number0``
desc0
``{unnamed_struct}``
anonymous
``number1``
desc1
``{unnamed_struct}``
anonymous
``number2``
desc2
To test patch [2/2], just replace __packed for
____cacheline_aligned_in_smp and compare how, at the previous stage the
script believes ____cacheline... is an alias for the struct and after
the patch it is removed just as the others attributes.
Finally, I have compared the output of "make htmldocs" with and without
this patch. No new warning were found and one warning regarding
____cacheline_aligned_in_smp at include/linux/netdevice.h was removed.
Thanks,
André
André Almeida (2):
kernel-doc: fix processing nested structs with attributes
kernel-doc: add support for ____cacheline_aligned_in_smp attribute
scripts/kernel-doc | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
--
2.23.0
next reply other threads:[~2019-09-17 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 19:41 André Almeida [this message]
2019-09-17 19:41 ` [PATCH 1/2] kernel-doc: fix processing nested structs with attributes André Almeida
2019-09-17 19:41 ` [PATCH 2/2] kernel-doc: add support for ____cacheline_aligned_in_smp attribute André Almeida
2019-10-01 13:04 ` Jonathan Corbet
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=20190917194146.35642-1-andrealmeid@collabora.com \
--to=andrealmeid@collabora.com \
--cc=corbet@lwn.net \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®