public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: "Luís Henriques" <lhenriques@criticalsoftware.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>, linux-kernel@vger.kernel.org
Subject: Re: copy to suer space
Date: Tue, 20 Nov 2001 11:41:24 -0700	[thread overview]
Message-ID: <20011120114124.T1308@lynx.no> (raw)
In-Reply-To: <5.1.0.14.2.20011120165440.00a745b0@pop.cus.cam.ac.uk> <200111201714.fAKHEc276467@criticalsoftware.com>
In-Reply-To: <200111201714.fAKHEc276467@criticalsoftware.com>; from lhenriques@criticalsoftware.com on Tue, Nov 20, 2001 at 05:08:52PM +0000

On Nov 20, 2001  17:08 +0000, Luís Henriques wrote:
> > I don't think what you are trying to do is possible. Even if you somehow
> > managed to write over the code segment of a user space process (which I
> > very much doubt would be possible as I assume the memory is mapped
> > read-only)
> 
> Is there a way to solve this problem? To temporarly turn it read/write?
> 
> >, as soon as the kernel pages out (i.e. discards!) some portion
> > of the executable due to memory shortage your changes would be lost, since
> > the paging back into memory would happen by reading the executable back
> > from disk, which would mean it would read the unmodified code into
> > memory...
> 
> When I'm modifing the code, I'm sure that the page is in memory because my 
> code is called from the user space, in the exact location where I want to 
> change it (with a breakpoint interruption...)
> 
> The point is that I can't write to the memory location I want... How do I 
> solve this?

Maybe if you describe the actual problem that you are trying to solve, and
not the actual way you are trying to solve it, there may be a better method.
Usually, if something you are trying to do is very hard to do, there is a
different (much better) way of doing it.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2001-11-20 18:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.31.0111201637420.13674-100000@mail.deis.isec.pt >
2001-11-20 17:02 ` copy to suer space Anton Altaparmakov
2001-11-20 17:08   ` Luís Henriques
2001-11-20 18:41     ` Andreas Dilger [this message]
2001-11-20 18:44       ` Luís Henriques
2001-11-20 18:58         ` Hua Zhong
2001-11-20 19:39         ` Andreas Dilger
2001-11-21  0:06           ` Mike Fedyk
2001-11-21 10:52             ` Luís Henriques
2001-11-23 13:14               ` Juan Quintela
2001-11-23 14:35                 ` Luís Henriques
2001-11-23 23:53                   ` H. Peter Anvin
2001-11-20 17:37   ` Anton Altaparmakov
2001-11-20 17:53     ` Luís Henriques
2001-11-20 18:18       ` Nick LeRoy
2001-11-22 18:51       ` Andreas Bombe
2001-11-20 18:09   ` Luís Henriques
2001-11-21 14:37 Joerg Pommnitz
     [not found] <sbfa4d3a.051@MAIL-SMTP.uvsc.edu>
2001-11-21 10:49 ` Luís Henriques
  -- strict thread matches above, loose matches on Subject: below --
2001-11-20 16:40 Luis Miguel Correia Henriques

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=20011120114124.T1308@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=aia21@cam.ac.uk \
    --cc=lhenriques@criticalsoftware.com \
    --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