linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Stephen Hemminger <shemminger@osdl.org>,
	linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: 2.6.11-rc3: Kylix application no longer works?
Date: Wed, 9 Feb 2005 10:34:41 -0500	[thread overview]
Message-ID: <20050209153441.GA8809@nevyn.them.org> (raw)
In-Reply-To: <20050208181018.5592beab.akpm@osdl.org>

On Tue, Feb 08, 2005 at 06:10:18PM -0800, Andrew Morton wrote:
> We could just remove the printk and stick a comment over it.  If the
> application later tries to access the not-there pages then it'll just
> fault.
> 
> However I worry if there is some way in which we can leave unzeroed memory
> accessible to the application, although it's hard to see how that could
> happen.
> 
> Daniel, Pavel cruelly chopped you off the Cc when replying.  What's your
> diagnosis on the below?

It's asking for a lot of unwritable zeroed space.  See this:

>   LOAD           0x000000 0x08048000 0x08048000 0xb7354 0x1b7354 R E 0x1000
>   LOAD           0x0b7354 0x08200354 0x08200354 0x1e3e4 0x1f648 RW  0x1000

The 0xb7354 is size to map from the file, the 0x1b7354 is size to map
in memory.  We're supposed to zero-fill the rest.  Now that I think
about it I can see why this is a problem - the kernel probably assumes
that any segment with MemSiz > FileSiz will be writable.  Certainly
it's a bit weird for the app to request unwritable zeroed pages.

clear_user's probably not the right way to provide the extra zeroing.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  parent reply	other threads:[~2005-02-09 15:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 22:11 2.6.11-rc3: Kylix application no longer works? Pavel Machek
2005-02-07 22:51 ` Andrew Morton
2005-02-08  0:03   ` Daniel Drake
2005-02-08  0:18     ` Andrew Morton
2005-02-08  0:56       ` Grzegorz Kulewski
2005-02-08  4:06         ` Andrew Morton
2005-02-08 17:13           ` Pavel Machek
2005-02-08  8:15       ` Daniel Drake
2005-02-08 17:27   ` Pavel Machek
2005-02-08 17:51   ` Pavel Machek
2005-02-08 19:16     ` Stephen Hemminger
2005-02-09  2:10       ` Andrew Morton
2005-02-09 11:11         ` Pavel Machek
2005-02-09 15:34         ` Daniel Jacobowitz [this message]
2005-02-09 20:13           ` Rik van Riel
2005-02-12  0:39             ` Ingo Oeser
2005-02-08 20:43     ` Daniel Jacobowitz
2005-02-08 22:27       ` Pavel Machek

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=20050209153441.GA8809@nevyn.them.org \
    --to=dan@debian.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).