From: Andrea Arcangeli <andrea@e-mind.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Zlatko.Calusic@CARNet.hr, Linux-MM List <linux-mm@kvack.org>,
Andi Kleen <andi@zero.aec.at>
Subject: Re: Update shared mappings
Date: Tue, 1 Dec 1998 18:48:44 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.3.96.981201182728.16745C-100000@dragon.bogus> (raw)
In-Reply-To: <199812011503.PAA18144@dax.scot.redhat.com>
On Tue, 1 Dec 1998, Stephen C. Tweedie wrote:
>I think I have: I can reliably deadlock machines with this patch.
s/patch/proggy/ side effect of lots of kernel developing ;)
andrea@dragon:/tmp$ egcc -O2 shared_map.c
andrea@dragon:/tmp$ ./a.out
andrea@dragon:/tmp$
No deadlock at all. Are you sure you are using my _latest_ patch in
arca-39? Some weeks ago I fixed this:
static void update_shared_mappings(struct vm_area_struct *this,
unsigned long address,
pte_t orig_pte)
{
if (this->vm_flags & VM_SHARED)
{
struct file * filp = this->vm_file;
if (filp)
{
struct inode * inode = filp->f_dentry->d_inode;
struct vm_area_struct * shared;
for (shared = inode->i_mmap; shared;
shared = shared->vm_next_share)
{
if (shared->vm_mm == this->vm_mm)
^^^^^ ^^^^^
continue;
update_one_shared_mapping(shared, address,
orig_pte);
}
}
}
}
--
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-12-01 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-20 4:10 Zlatko Calusic
1998-11-30 13:52 ` Stephen C. Tweedie
1998-11-30 15:19 ` Zlatko Calusic
1998-11-30 20:02 ` Andrea Arcangeli
1998-12-01 15:03 ` Stephen C. Tweedie
1998-12-01 17:48 ` Andrea Arcangeli [this message]
1998-12-02 16:21 ` Stephen C. Tweedie
1998-12-02 18:32 ` Andrea Arcangeli
1998-12-03 5:44 ` Eric W. Biederman
1998-12-03 11:56 ` Stephen C. Tweedie
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.981201182728.16745C-100000@dragon.bogus \
--to=andrea@e-mind.com \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=andi@zero.aec.at \
--cc=linux-mm@kvack.org \
--cc=sct@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