mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Elder <elder@linaro.org>
To: check.kernel@gmail.com, Anton Vorontsov <anton@enomsg.org>,
	Colin Cross <ccross@android.com>,
	Kees Cook <keescook@chromium.org>,
	Tony Luck <tony.luck@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Petr Mladek <pmladek@suse.cz>,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	Peter Hurley <peter@hurleysoftware.com>,
	Joe Perches <joe@perches.com>, Tejun Heo <tj@kernel.org>,
	Ethan du <duhui@xiaomi.com>, Linghua Gu <gulinghua@xiaomi.com>
Cc: linux-kernel@vger.kernel.org, yangdongdong <yangdongdong@xiaomi.com>
Subject: Re: [PATCH] fs/pstore: provide panic data even in suspend
Date: Wed, 05 Aug 2015 08:23:07 -0500	[thread overview]
Message-ID: <55C20E3B.5040102@linaro.org> (raw)
In-Reply-To: <1438780270-12024-1-git-send-email-check.kernel@gmail.com>

On 08/05/2015 08:11 AM, check.kernel@gmail.com wrote:
> From: yangdongdong <yangdongdong@xiaomi.com>
> 
> This also enables panic and oops messages which
> in suspend context to be logged into ramoops console
> buffer where it can be read back at some later point.
> 
> Signed-off-by: yangdongdong <yangdongdong@xiaomi.com>
> Signed-off-by: gulinghua <gulinghua@xiaomi.com>

I have a small comment on the code below.

					-Alex

> ---
>  fs/pstore/ram.c            | 21 +++++++++++++++++++++
>  include/linux/pstore_ram.h |  1 +
>  kernel/printk/printk.c     |  6 ++++++
>  3 files changed, 28 insertions(+)
> 
> diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
> index 6c26c4d..f84c5ab 100644
> --- a/fs/pstore/ram.c
> +++ b/fs/pstore/ram.c
> @@ -642,8 +642,28 @@ static void ramoops_register_dummy(void)
>  	}
>  }
>  
> +static int ramoops_console_notify(struct notifier_block *this,
> +		unsigned long event, void *ptr)
> +{
> +	pr_emerg("ramoops unlock console ...\n");
> +	emergency_unlock_console();
> +
> +	return 0;
> +}
> +
> +static struct notifier_block ramoop_nb = {
> +	.notifier_call = ramoops_console_notify,
> +	.priority = INT_MAX,
> +};
> +
> +static void ramoops_prepare(void)
> +{
> +	atomic_notifier_chain_register(&panic_notifier_list, &ramoop_nb);
> +}
> +
>  static int __init ramoops_init(void)
>  {
> +	ramoops_prepare();
>  	ramoops_register_dummy();
>  	return platform_driver_register(&ramoops_driver);
>  }
> @@ -654,6 +674,7 @@ static void __exit ramoops_exit(void)
>  	platform_driver_unregister(&ramoops_driver);
>  	platform_device_unregister(dummy);
>  	kfree(dummy_data);
> +	atomic_notifier_chain_unregister(&panic_notifier_list, &ramoop_nb);

I would say either wrap this atomic_notificer_chain_unregister()
call in a trivial function ramoops_unprepare(), or (preferably)
get rid of ramoops_prepare().

>  }
>  module_exit(ramoops_exit);
>  
> diff --git a/include/linux/pstore_ram.h b/include/linux/pstore_ram.h
> index 9c9d6c1..826a35b 100644
> --- a/include/linux/pstore_ram.h
> +++ b/include/linux/pstore_ram.h
> @@ -52,6 +52,7 @@ struct persistent_ram_zone {
>  	size_t old_log_size;
>  };
>  
> +extern void emergency_unlock_console(void);
>  struct persistent_ram_zone *persistent_ram_new(phys_addr_t start, size_t size,
>  			u32 sig, struct persistent_ram_ecc_info *ecc_info,
>  			unsigned int memtype);
> diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> index cf8c242..ece645c 100644
> --- a/kernel/printk/printk.c
> +++ b/kernel/printk/printk.c
> @@ -2107,6 +2107,12 @@ void resume_console(void)
>  	console_unlock();
>  }
>  
> +void emergency_unlock_console(void)
> +{
> +	resume_console();
> +}
> +EXPORT_SYMBOL(emergency_unlock_console);
> +
>  /**
>   * console_cpu_notify - print deferred console messages after CPU hotplug
>   * @self: notifier struct
> 


  reply	other threads:[~2015-08-05 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 13:11 check.kernel
2015-08-05 13:23 ` Alex Elder [this message]
2015-08-05 14:42 check.kernel

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=55C20E3B.5040102@linaro.org \
    --to=elder@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=anton@enomsg.org \
    --cc=ccross@android.com \
    --cc=check.kernel@gmail.com \
    --cc=duhui@xiaomi.com \
    --cc=gulinghua@xiaomi.com \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@suse.com \
    --cc=peter@hurleysoftware.com \
    --cc=pmladek@suse.cz \
    --cc=tj@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=yangdongdong@xiaomi.com \
    /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®