public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Pavel Machek <pavel@ucw.cz>,
	Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Oops in swsusp
Date: Mon, 11 Apr 2005 19:02:25 +0200	[thread overview]
Message-ID: <200504111902.25900.rjw@sisk.pl> (raw)
In-Reply-To: <425A9F6A.8080200@domdv.de>

Hi,

On Monday, 11 of April 2005 18:01, Andreas Steinmetz wrote:
> Rafael J. Wysocki wrote:
> > Hi,
> > 
> > On Monday, 11 of April 2005 01:17, Andreas Steinmetz wrote:
> > 
> >>Pavel,
> >>during testing of the encrypted swsusp_image on x86_64 I did get an Oops
> >>from time to time at memcpy+11 called from swsusp_save+1090 which turns
> >>out to be the memcpy in copy_data_pages() of swsusp.c.
> >>The Oops is caused by a NULL pointer (I don't remember if it was source
> >>or destination).
> > 
> > 
> > It's quite important, however.  If it's the destination, it's probably a bug in
> > swsusp.  Otherwise, the problem is more serious.  Could you, please,
> > add BUG_ON(!pbe->address) right before the memcpy() and retest?
> 
> Here's the result:
> 
> BUG_ON(!pbe->address) hits, so is seems to be a swsusp problem.
> 
> So I added a BUG_ON(!to_copy) as shown below (mangled for mailing):
> 
> if (saveable(zone, &zone_pfn)) {
>        struct page * page;
>        BUG_ON(!to_copy);
>        page = pfn_to_page(zone_pfn + zone->zone_start_pfn);
>        pbe->orig_address = (long) page_address(page);
>        /* copy_page is not usable for copying task structs. */
>        BUG_ON(!pbe->address);
>        memcpy((void *)pbe->address, (void *)pbe->orig_address,
>               PAGE_SIZE);
>        pbe++;
>        to_copy--;
> }
> 
> The BUG_ON(!to_copy) hits, too.

Oh, I see.  You have discovered a bug in the code that was replaced
in 2.6.12-rc1. :-)  Please use 2.6.12-rc2 or the latest -mm for
testing/development of swsusp.

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-04-11 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10 23:17 Oops in swsusp Andreas Steinmetz
2005-04-11  6:59 ` Rafael J. Wysocki
2005-04-11 13:09   ` Andreas Steinmetz
2005-04-11 16:01   ` Andreas Steinmetz
2005-04-11 17:02     ` Rafael J. Wysocki [this message]
2005-04-11 11:00 ` Pavel Machek

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=200504111902.25900.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=ast@domdv.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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