From: "Bjørn Mork" <bjorn@mork.no>
To: Joerg Roedel <jroedel@suse.de>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>, linux-pm@vger.kernel.org
Subject: Re: NULL pointer dereference in swsusp_free with 3.17-rc5
Date: Wed, 24 Sep 2014 12:17:18 +0200 [thread overview]
Message-ID: <87vbodiaq9.fsf@nemi.mork.no> (raw)
In-Reply-To: <20140924095111.GC10438@suse.de> (Joerg Roedel's message of "Wed, 24 Sep 2014 11:51:11 +0200")
Joerg Roedel <jroedel@suse.de> writes:
>> @@ -1343,7 +1343,15 @@ void swsusp_free(void)
>> {
>> unsigned long fb_pfn, fr_pfn;
>>
>> +WARN_ON(!forbidden_pages_map);
>> +if (!forbidden_pages_map)
>> + return;
>> +
>> memory_bm_position_reset(forbidden_pages_map);
>> +WARN_ON(!free_pages_map);
>> +if (!free_pages_map)
>> + return;
>> +
>> memory_bm_position_reset(free_pages_map);
>
> ... the old code did not check for a valid forbidden_pages_map and
> free_pages_map either, so it should crash there too.
Well, it did test AFAICS... The 3.16 code is
int swsusp_page_is_forbidden(struct page *page)
{
return forbidden_pages_map ?
memory_bm_test_bit(forbidden_pages_map, page_to_pfn(page)) : 0;
}
..
void swsusp_free(void)
{
..
if (swsusp_page_is_forbidden(page) &&
swsusp_page_is_free(page)) {
swsusp_unset_page_forbidden(page);
swsusp_unset_page_free(page);
__free_page(page);
}
Bjørn
next prev parent reply other threads:[~2014-09-24 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 14:50 NULL pointer dereference in swsusp_free with 3.17-rc5 Bjørn Mork
2014-09-23 15:24 ` Rafael J. Wysocki
2014-09-23 17:27 ` Bjørn Mork
2014-09-23 20:28 ` Rafael J. Wysocki
2014-09-24 9:46 ` Joerg Roedel
2014-09-23 21:20 ` Rafael J. Wysocki
2014-09-24 7:45 ` Bjørn Mork
2014-09-24 9:51 ` Joerg Roedel
2014-09-24 10:17 ` Bjørn Mork [this message]
2014-09-24 23:44 ` Rafael J. Wysocki
2014-09-25 7:20 ` Bjørn Mork
2014-09-25 9:13 ` Joerg Roedel
2014-09-25 10:54 ` Bjørn Mork
2014-09-25 20:26 ` Rafael J. Wysocki
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=87vbodiaq9.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=jroedel@suse.de \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.