From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mm@kvack.org
Cc: bugme-daemon@bugzilla.kernel.org, drow@false.org,
Roland McGrath <roland@redhat.com>,
Oleg Nesterov <oleg@tv-sign.ru>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [Bugme-new] [Bug 11110] New: Core dumps do not include writable unmodified MAP_PRIVATE maps
Date: Thu, 17 Jul 2008 13:23:17 -0700 [thread overview]
Message-ID: <20080717132317.96e73124.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-11110-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Thu, 17 Jul 2008 11:57:08 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=11110
>
> Summary: Core dumps do not include writable unmodified
> MAP_PRIVATE maps
> Product: Process Management
> Version: 2.5
> KernelVersion: 2.6.26
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: process_other@kernel-bugs.osdl.org
> ReportedBy: drow@false.org
> CC: davem@davemloft.net
>
>
> Latest working kernel version: Not sure.
> Earliest failing kernel version: Been failing at least since April 2006.
> Passed at some point previous to that, probably 2.4.
> Distribution: Debian
> Hardware Environment: x86_64 SMP
> Software Environment: GDB testsuite
> Problem Description:
>
> The test corefile.exp fails because it maps a file and then core dumps,
> expecting the mapped contents to be in the core dump. The mapping is made with
> these options:
>
> buf2 = (char *) mmap (0, MAPSIZE, PROT_READ | PROT_WRITE, MAP_PRIVATE, fd,
> 0);
>
> Any page that has been touched will be dumped, any unmodified page will not be.
>
> I've discussed this with David Miller a couple of times; last time I recall was
> in January 2007.
>
> Steps to reproduce:
>
> Run coremaker from the GDB testsuite (attached). Load the core file into GDB
> and try to print buf2.
>
Does anyone recall whether this is deliberate behaviour, or did we just goof?
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2008-07-17 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11110-10286@http.bugzilla.kernel.org/>
2008-07-17 20:23 ` Andrew Morton [this message]
2008-07-17 20:39 ` Neil Horman
2008-07-17 21:20 ` Daniel Jacobowitz
2008-07-17 22:13 ` Roland McGrath
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=20080717132317.96e73124.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=drow@false.org \
--cc=linux-mm@kvack.org \
--cc=nhorman@tuxdriver.com \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
/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