From: Rusty Russell <rusty@rustcorp.com.au>
To: Sebastian Wankerl <sisewank@cip.cs.fau.de>, linux-kernel@vger.kernel.org
Cc: Sebastian Wankerl <sisewank@cip.cs.fau.de>,
Philip Kranz <philip.kranz@googlemail.com>
Subject: Re: [PATCH] Add non-zero module sections to sysfs
Date: Thu, 04 Apr 2013 11:30:38 +1030 [thread overview]
Message-ID: <87mwtf3ya1.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1364994499-23708-1-git-send-email-sisewank@cip.cs.fau.de>
Sebastian Wankerl <sisewank@cip.cs.fau.de> writes:
> Add non-zero module sections to sysfs on architectures unequal to PARISC.
> KGDB needs all module sections for proper module debugging. Therefore, commit
> 35dead4235e2b67da7275b4122fed37099c2f462 is revoked except for PARISC
> architecture.
#ifdef CONFIG_PARISC in the middle of kernel/module.c is super-ugly, and
wrong.
My preference would be to fix kgdb. If the section is empty, what need
does it have to examine it?
Thanks,
Rusty.
> Signed-off-by: Sebastian Wankerl <sisewank@cip.cs.fau.de>
> Signed-off-by: Philip Kranz <philip.kranz@googlemail.com>
>
> ---
> kernel/module.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 3c2c72d..5393a54 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -1316,7 +1316,11 @@ resolve_symbol_wait(struct module *mod,
> #ifdef CONFIG_KALLSYMS
> static inline bool sect_empty(const Elf_Shdr *sect)
> {
> +#if defined(CONFIG_PARISC)
> return !(sect->sh_flags & SHF_ALLOC) || sect->sh_size == 0;
> +#else
> + return !(sect->sh_flags & SHF_ALLOC);
> +#endif
> }
>
> struct module_sect_attr
> --
> 1.7.10.4
next prev parent reply other threads:[~2013-04-04 3:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 13:08 [PATCH] Add non-zero module sections to sysfs Sebastian Wankerl
2013-04-04 1:00 ` Rusty Russell [this message]
2013-04-04 9:40 ` Sebastian Wankerl
2013-04-05 4:00 ` Rusty Russell
2013-04-05 9:40 ` Sebastian Wankerl
2013-04-05 10:07 ` James Bottomley
2013-04-06 4:52 ` Rusty Russell
2013-04-06 10:52 ` James Bottomley
2013-04-06 15:16 ` John David Anglin
2013-04-07 1:22 ` James Bottomley
2013-04-07 1:45 ` John David Anglin
2013-04-06 10:40 ` Philip Kranz
2013-04-08 4:14 ` Rusty Russell
2013-04-08 11:55 ` Philip Kranz
2013-04-11 14:11 ` Philip Kranz
2013-04-05 14:56 ` Sebastian Wankerl
2013-04-06 4:31 ` Rusty Russell
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=87mwtf3ya1.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=philip.kranz@googlemail.com \
--cc=sisewank@cip.cs.fau.de \
/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