From: Randy Dunlap <rdunlap@infradead.org>
To: Cong Wang <amwang@redhat.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next] netconsole: add oops_only module option
Date: Thu, 08 Nov 2012 11:49:33 -0800 [thread overview]
Message-ID: <509C0CCD.7020900@infradead.org> (raw)
In-Reply-To: <1352382158-3928-1-git-send-email-amwang@redhat.com>
On 11/08/2012 05:42 AM, Cong Wang wrote:
> Some people wants to log only oops messages via netconsole,
> (this is also why netoops was invented)
> so add a module option for netconsole. This can be tuned
> via /sys/module/netconsole/parameters/oops_only at run time
> as well.
>
Hi,
What does this do with panics?
Do they set oops_in_progress?
thanks.
> Cc: David Miller <davem@davemloft.net>
> Signed-off-by: Cong Wang <amwang@redhat.com>
>
> ---
> diff --git a/drivers/net/netconsole.c b/drivers/net/netconsole.c
> index b332112..6989ebe 100644
> --- a/drivers/net/netconsole.c
> +++ b/drivers/net/netconsole.c
> @@ -56,6 +56,10 @@ static char config[MAX_PARAM_LENGTH];
> module_param_string(netconsole, config, MAX_PARAM_LENGTH, 0);
> MODULE_PARM_DESC(netconsole, " netconsole=[src-port]@[src-ip]/[dev],[tgt-port]@<tgt-ip>/[tgt-macaddr]");
>
> +static bool oops_only = false;
> +module_param(oops_only, bool, 0600);
> +MODULE_PARM_DESC(oops_only, "Only log oops messages");
> +
> #ifndef MODULE
> static int __init option_setup(char *opt)
> {
> @@ -683,6 +687,8 @@ static void write_msg(struct console *con, const char *msg, unsigned int len)
> struct netconsole_target *nt;
> const char *tmp;
>
> + if (oops_only && !oops_in_progress)
> + return;
> /* Avoid taking lock and disabling interrupts unnecessarily */
> if (list_empty(&target_list))
> return;
> --
--
~Randy
next prev parent reply other threads:[~2012-11-08 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 13:42 [PATCH net-next] netconsole: add oops_only module option Cong Wang
2012-11-08 19:49 ` Randy Dunlap [this message]
2012-11-09 3:02 ` Cong Wang
2012-11-09 3:07 ` David Miller
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=509C0CCD.7020900@infradead.org \
--to=rdunlap@infradead.org \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.