From: "Stephen C. Tweedie" <sct@redhat.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
Daniel Phillips <phillips@innominate.de>,
linux-kernel@vger.kernel.org
Subject: Re: Subtle MM bug
Date: Thu, 11 Jan 2001 19:47:53 +0000 [thread overview]
Message-ID: <20010111194753.P25375@redhat.com> (raw)
In-Reply-To: <20010111141330.H25375@redhat.com> <Pine.GSO.4.21.0101111401430.17363-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0101111401430.17363-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Thu, Jan 11, 2001 at 02:03:48PM -0500
Hi,
On Thu, Jan 11, 2001 at 02:03:48PM -0500, Alexander Viro wrote:
> On Thu, 11 Jan 2001, Stephen C. Tweedie wrote:
>
> > On Thu, Jan 11, 2001 at 02:12:05PM +0100, Trond Myklebust wrote:
> > >
> > > What's wrong with copy-on-write style semantics? IOW, anyone who
> > > wants to change the credentials needs to make a private copy of the
> > > existing structure first.
> >
> > Because COW only solves the problem if each task is only changing its
> > own, local, private copy of the credentials. Posix threads demand
> > that one thread changing credentials also affects all the other
> > threads immediately, and making your own local private copy won't help
> > you to change the other tasks' credentials safely.
>
> And how is that different from the current situation?
It's not, which is the point I was making: COW doesn't actually solve
the pthreads problem. Far better to do it in user space.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 19:51 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 5:29 Subtle MM bug Wayne Whitney
2001-01-08 5:42 ` Andi Kleen
2001-01-08 6:04 ` Linus Torvalds
2001-01-08 17:44 ` Rik van Riel
2001-01-08 18:02 ` Linus Torvalds
2001-01-08 17:16 ` Rik van Riel
2001-01-08 17:58 ` Linus Torvalds
2001-01-08 23:41 ` Zlatko Calusic
2001-01-09 2:58 ` Linus Torvalds
2001-01-09 6:20 ` Eric W. Biederman
2001-01-09 7:27 ` Linus Torvalds
2001-01-09 11:38 ` Eric W. Biederman
2001-01-09 12:29 ` Zlatko Calusic
2001-01-09 18:47 ` Linus Torvalds
2001-01-09 19:09 ` Daniel Phillips
2001-01-09 19:29 ` Trond Myklebust
2001-01-10 17:32 ` Andi Kleen
2001-01-10 19:31 ` Alan Cox
2001-01-10 19:33 ` Andi Kleen
2001-01-10 19:40 ` Alan Cox
2001-01-10 19:43 ` Andi Kleen
2001-01-10 19:48 ` Alan Cox
2001-01-10 19:48 ` Andi Kleen
2001-01-11 9:51 ` Trond Myklebust
2001-01-10 20:11 ` Linus Torvalds
2001-01-11 12:56 ` Stephen C. Tweedie
2001-01-11 13:10 ` Andi Kleen
2001-01-11 13:12 ` Trond Myklebust
2001-01-11 14:13 ` Stephen C. Tweedie
2001-01-11 19:03 ` Alexander Viro
2001-01-11 19:47 ` Stephen C. Tweedie [this message]
2001-01-11 19:57 ` Alexander Viro
2001-01-11 16:50 ` Albert D. Cahalan
2001-01-11 17:35 ` Stephen C. Tweedie
2001-01-11 19:38 ` Albert D. Cahalan
2001-01-11 19:01 ` Alexander Viro
2001-01-09 19:37 ` Linus Torvalds
2001-01-17 8:46 ` Rik van Riel
2001-01-25 22:51 ` Daniel Phillips
2001-01-09 19:53 ` Simon Kirby
2001-01-09 20:08 ` Linus Torvalds
2001-01-09 20:10 ` Zlatko Calusic
2001-01-10 1:45 ` David Woodhouse
2001-01-10 2:26 ` Andrea Arcangeli
2001-01-10 6:57 ` Linus Torvalds
2001-01-10 11:46 ` David Woodhouse
2001-01-10 14:56 ` Andrea Arcangeli
2001-01-10 17:46 ` Eric W. Biederman
2001-01-10 18:33 ` Andrea Arcangeli
2001-01-17 14:26 ` Rik van Riel
2001-01-10 19:03 ` Linus Torvalds
2001-01-10 19:27 ` David S. Miller
2001-01-10 19:36 ` Alan Cox
2001-01-10 23:56 ` David Weinehall
2001-01-11 0:24 ` Alan Cox
2001-01-12 5:56 ` Ralf Baechle
2001-01-12 16:10 ` Eric W. Biederman
2001-01-12 21:11 ` Russell King
2001-01-15 2:56 ` Ralf Baechle
2001-01-15 6:59 ` Eric W. Biederman
2001-01-15 2:53 ` Ralf Baechle
2001-01-15 8:41 ` Caches, page coloring, virtual indexed caches, and more Eric W. Biederman
2001-01-15 11:54 ` Ralf Baechle
2001-01-15 12:53 ` Anton Blanchard
2001-01-15 17:41 ` Ralf Baechle
2001-01-17 4:36 ` Anton Blanchard
2001-01-16 9:34 ` Eric W. Biederman
2001-01-17 4:43 ` Anton Blanchard
2001-01-17 8:35 ` Eric W. Biederman
2001-01-15 17:16 ` Eric W. Biederman
2001-01-16 4:58 ` Ralf Baechle
2001-01-15 18:22 ` Jamie Lokier
2001-01-15 12:51 ` Anton Blanchard
2001-01-17 14:28 ` Subtle MM bug Rik van Riel
2001-01-18 1:23 ` Linus Torvalds
2001-01-18 11:48 ` Rik van Riel
2001-01-10 17:03 ` Linus Torvalds
2001-01-11 14:36 ` Jim Gettys
2001-01-08 21:30 ` Wayne Whitney
-- strict thread matches above, loose matches on Subject: below --
2001-01-10 19:57 Chris Wing
2001-01-08 20:39 Szabolcs Szakacsits
2001-01-08 21:56 ` Wayne Whitney
2001-01-08 23:22 ` Wayne Whitney
2001-01-08 23:30 ` Andrea Arcangeli
2001-01-09 0:37 ` Linus Torvalds
2001-01-08 22:00 ` Wayne Whitney
2001-01-08 22:15 ` Andrea Arcangeli
2001-01-07 20:59 Zlatko Calusic
2001-01-07 21:37 ` Rik van Riel
2001-01-07 22:33 ` Zlatko Calusic
2001-01-09 2:01 ` Zlatko Calusic
2001-01-17 4:48 ` Rik van Riel
2001-01-17 18:53 ` Zlatko Calusic
2001-01-18 1:32 ` Rik van Riel
2001-04-17 19:37 ` H. Peter Anvin
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=20010111194753.P25375@redhat.com \
--to=sct@redhat.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@innominate.de \
--cc=torvalds@transmeta.com \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@math.psu.edu \
/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