From: Linus Torvalds <torvalds@transmeta.com>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>
Cc: Bill Hawes <whawes@transmeta.com>,
Linux-kernel <linux-kernel@vger.rutgers.edu>,
linux-mm@kvack.org
Subject: Re: writable swap cache explained (it's weird)
Date: Thu, 30 Jul 1998 14:25:57 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.3.96.980730142318.6696A-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.3.95.980730150740.17264B-100000@as200.spellcast.com>
On Thu, 30 Jul 1998, Benjamin C.R. LaHaise wrote:
>
> (a) sounds like the Obvious Thing To Do in the mmap method for /proc, but
> will break xdos. Wtf were they thinking in writing that insane code?
> Hmmm, this bug probably applies to 2.0 too.... in a much more subtle
> fashion.
The insane code is indeed insane, but I think I understand why they did
it: they didn't want to mess around with sysv shared memory regions.
I'd love to just completely get rid of mmap() on /proc/self/mem, because
it actually is a bad idea completely (not just the shared mappings - even
a private mapping of another mapping that is shared has simply completely
untenable logical problems).
I'd much more prefer for somebody to take the time to change dosemu to use
the standard (and supported) sysv shared memory setup than to make any
kernel changes..
Linus
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-07-30 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35BF43AC.F0F0C14F@transmeta.com>
1998-07-30 19:20 ` Benjamin C.R. LaHaise
1998-07-30 19:49 ` Bill Hawes
1998-07-30 21:25 ` Linus Torvalds [this message]
1998-07-30 23:14 ` Richard Gooch
1998-08-02 4:54 ` Eric W Biederman
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=Pine.LNX.3.96.980730142318.6696A-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=blah@kvack.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=whawes@transmeta.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