From: Rusty Russell <rusty@rustcorp.com.au>
To: Laura Abbott <labbott@fedoraproject.org>
Cc: Laura Abbott <labbott@fedoraproject.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] module: Limit line length of module prints
Date: Fri, 11 Dec 2015 20:09:40 +1030 [thread overview]
Message-ID: <87a8phgw83.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1449798632-29248-1-git-send-email-labbott@fedoraproject.org>
Laura Abbott <labbott@fedoraproject.org> writes:
> print_modules currently uses pr_cont to print all module information.
> This has the side effect of printing lots of modules on one very long
> line. This makes copy/pasting oopses more effort if manual wrapping is
> required. Place a reasonable limit (80 chars) on the number of modules
> on each line.
>
> Signed-off-by: Laura Abbott <labbott@fedoraproject.org>
> ---
> Does this bother anyone else or am I the only one who hates dealing
> with the long lines of "Modules linked in"?
Never bothered me, but I'm a bit odd :) I worry more about the effect
on machine parsing.
Cheers,
Rusty.
> ---
> kernel/module.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/module.c b/kernel/module.c
> index 8f051a1..ace82f1 100644
> --- a/kernel/module.c
> +++ b/kernel/module.c
> @@ -4059,11 +4059,14 @@ struct module *__module_text_address(unsigned long addr)
> }
> EXPORT_SYMBOL_GPL(__module_text_address);
>
> +#define MAX_LINE_CHARS 80
> +
> /* Don't grab lock, we're oopsing. */
> void print_modules(void)
> {
> struct module *mod;
> char buf[8];
> + int cnt = 0;
>
> printk(KERN_DEFAULT "Modules linked in:");
> /* Most callers should already have preempt disabled, but make sure */
> @@ -4071,7 +4074,13 @@ void print_modules(void)
> list_for_each_entry_rcu(mod, &modules, list) {
> if (mod->state == MODULE_STATE_UNFORMED)
> continue;
> - pr_cont(" %s%s", mod->name, module_flags(mod, buf));
> +
> + if (cnt > MAX_LINE_CHARS) {
> + cnt = 0;
> + pr_cont("\n");
> + }
> +
> + cnt += pr_cont(" %s%s", mod->name, module_flags(mod, buf));
> }
> preempt_enable();
> if (last_unloaded_module[0])
> --
> 2.5.0
next prev parent reply other threads:[~2015-12-11 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 1:50 [RFC][PATCH] module: Limit line length of module prints Laura Abbott
2015-12-11 9:39 ` Rusty Russell [this message]
2015-12-11 22:25 ` Laura Abbott
2015-12-14 1:06 ` Rusty Russell
2015-12-15 22:47 ` Laura Abbott
[not found] ` <CAGG-pUT9stutifHDUyD8WiFaU5Ysp1vVaRpu7tShZEQEV+7Daw@mail.gmail.com>
2015-12-11 22:22 ` Laura Abbott
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=87a8phgw83.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=labbott@fedoraproject.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