Re: Oops in swsusp
From: Rafael J. Wysocki (rjw_at_sisk.pl)
Date: 04/11/05
- Previous message: bert hubert: "Re: more git updates.."
- In reply to: Andreas Steinmetz: "Oops in swsusp"
- Next in thread: Andreas Steinmetz: "Re: Oops in swsusp"
- Reply: Andreas Steinmetz: "Re: Oops in swsusp"
- Reply: Andreas Steinmetz: "Re: Oops in swsusp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Andreas Steinmetz <ast@domdv.de> Date: Mon, 11 Apr 2005 08:59:00 +0200
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?
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" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: bert hubert: "Re: more git updates.."
- In reply to: Andreas Steinmetz: "Oops in swsusp"
- Next in thread: Andreas Steinmetz: "Re: Oops in swsusp"
- Reply: Andreas Steinmetz: "Re: Oops in swsusp"
- Reply: Andreas Steinmetz: "Re: Oops in swsusp"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|