From: Pavel Machek <pavel@suse.cz>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Oops in swsusp
Date: Mon, 11 Apr 2005 13:00:23 +0200 [thread overview]
Message-ID: <20050411110023.GC1373@elf.ucw.cz> (raw)
In-Reply-To: <4259B425.4090105@domdv.de>
Hi!
> 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).
> This Oops seems to be unrelated to the encrypted image addition as I
> didn't touch any code in that area.
Could you still try to reproduce without any patches? Alocating memory
at wrong moment may cause something like that, and crypto routines
might do that.
Pavel
--
Boycott Kodak -- for their patent abuse against Java.
prev parent reply other threads:[~2005-04-11 11:00 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
2005-04-11 11:00 ` Pavel Machek [this message]
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=20050411110023.GC1373@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ast@domdv.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox