linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Chen Yu <yu.c.chen@intel.com>
Cc: joeyli <jlee@suse.com>, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][v6] PM / hibernate: Print the possible panic reason when resuming with inconsistent e820 map
Date: Fri, 26 Aug 2016 21:56:54 +0200	[thread overview]
Message-ID: <20160826195654.GD21442@amd> (raw)
In-Reply-To: <20160825110748.GA22104@sharon>

Hi!

> > > > What's the progress of this patch? Looks already have experts review it.
> > > > Why this patch didn't accept?
> > > This patch is a little overkilled, and I have saved another simpler
> > > version to only check the md5 hash (as people suggested) for it. I can post it later.
> > > 
> > 
> > I am happy to test and review it.
> >
> Here it is. As Rafael is on travel, it would be grateful
> if you can give some advance on this, thanks!

Better than last one.

> +#ifdef CONFIG_HIBERNATION_CHECK_E820
> +#define MD5_HASH_SIZE 128
> +
> +/**
> + *	get_e820_md5 - calculate md5 according to struct e820map
> + *
> + *	@map: the e820 map to be calculated
> + *	@buf: the md5 result to be stored to
> + */
> +static int get_e820_md5(struct e820map *map, void *buf)
> +{
> +	struct scatterlist sg;
> +	struct crypto_ahash *tfm;
> +	struct ahash_request *req;
> +	int ret = 0;
> +
> +	tfm = crypto_alloc_ahash("md5", 0, CRYPTO_ALG_ASYNC);
> +	if (IS_ERR(tfm))
> +		return -ENOMEM;
> +
> +	req = ahash_request_alloc(tfm, GFP_ATOMIC);

what context is this called from? GFP_ATOMIC allocations like to fail...

> +static int hibernation_e820_check(void *buf)
> +{
> +	int ret;
> +	char result[MD5_HASH_SIZE] = {0};
> +
> +	ret = get_e820_md5(&e820_saved, result);
> +	if (ret)
> +		return ret;
> +
> +	if (memcmp(result, buf, MD5_HASH_SIZE))
> +		e820_conflict = true;

Passing return value using global variable is ugly. Can you just print
the warning and kill the box here?
> +

> +	/*
> +	 * A page has been allocated previously to store the hibernation
> +	 * image header, so we can safely store the md5 result behind
> +	 * struct restore_data_record, with size of 128 bytes.
> +	 */
> +	hibernation_e820_save(addr + sizeof(struct restore_data_record));
> +

Please just allocate space in struct restore_data_record . And I don't
think md5 sum is 128 _bytes_.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2016-08-26 19:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21  5:21 [PATCH][v6] PM / hibernate: Print the possible panic reason when resuming with inconsistent e820 map Chen Yu
2016-08-23  9:45 ` joeyli
2016-08-23 10:01   ` Chen Yu
2016-08-24  1:36     ` joeyli
2016-08-25 11:07       ` Chen Yu
2016-08-26 19:56         ` Pavel Machek [this message]
2016-08-28  2:07           ` Chen Yu
2016-08-28 12:47             ` Pavel Machek
2016-08-28 13:08               ` Chen, Yu C
2016-08-28 13:15                 ` Pavel Machek
2016-08-28 13:34                   ` Chen, Yu C

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=20160826195654.GD21442@amd \
    --to=pavel@ucw.cz \
    --cc=jlee@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=yu.c.chen@intel.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;
as well as URLs for NNTP newsgroup(s).