From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: rjw@sisk.pl, linux-kernel@vger.kernel.org, akpm@zip.com.au,
agruen@suse.de
Subject: Re: Fix random crashes in x86-64 swsusp
Date: Thu, 7 Oct 2004 00:24:23 +0200 [thread overview]
Message-ID: <20041006222423.GB2630@elf.ucw.cz> (raw)
In-Reply-To: <20041006152533.514fb51b.akpm@osdl.org>
Hi!
> > Maybe we should memset freed memory to zero so such bugs are
> > prevented?
>
> It would make sense to poison these pages, yes. Zero would not be a good
> choice of value, actually - something like 0xbb would cause nice oopses if
> someone used a pointer which was backed by __init memory.
>
> CONFIG_DEBUG_PAGEALLOC will pick up this sort of bug, but that's i386-only.
Few minutes after that I found out that x86-64 has similar mechanism
under CONFIG_INIT_DEBUG... it uses 0xcc.
I just wonder if it should be configurable, memset over 100KB is not
likely to be noticeable.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2004-10-06 22:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 21:14 2.6.9-rc3[+recent swsusp patches]: swsusp kernel-preemption-unfriendly? Rafael J. Wysocki
2004-10-05 21:27 ` Pavel Machek
2004-10-06 8:55 ` Rafael J. Wysocki
2004-10-06 8:54 ` Pavel Machek
2004-10-06 10:06 ` Rafael J. Wysocki
2004-10-06 10:12 ` Pavel Machek
2004-10-06 21:46 ` Rafael J. Wysocki
2004-10-06 22:06 ` Fix random crashes in x86-64 swsusp Pavel Machek
2004-10-06 22:13 ` [kernel] " Andi Kleen
2004-10-06 22:25 ` Andrew Morton
2004-10-06 22:24 ` Pavel Machek [this message]
2004-10-08 20:59 ` swsusp: 8-order memory allocations problem (was: Re: Fix random crashes in x86-64 swsusp) Rafael J. Wysocki
2004-10-10 13:48 ` Pavel Machek
2004-10-10 18:28 ` Andrew Morton
2004-10-13 17:24 ` Rafael J. Wysocki
2004-10-14 15:37 ` swsusp: 8-order memory allocations problem (update) 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=20041006222423.GB2630@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.