From: Rajesh Venkatasubramanian <vrajesh@eecs.umich.edu>
To: Andrew Morton <akpm@osdl.org>
Cc: "David S. Miller" <davem@redhat.com>, hch@lst.de, linux-mm@kvack.org
Subject: Re: [PATCH] fix split_vma vs. invalidate_mmap_range_list race
Date: Sat, 4 Oct 2003 02:31:32 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0310040223230.27636-100000@cello.eecs.umich.edu> (raw)
In-Reply-To: <20031003224056.09421fb1.akpm@osdl.org>
>
> It looks OK. I updated the VM lock ranking docco to cover this.
> *
> + * ->i_sem
> + * ->i_shared_sem (truncate->invalidate_mmap_range)
> + *
I don't understand how my patch introduced this new(?) ordering.
My patch does not introduce any new semaphores or spin_locks in
any code path. Am I missing something ? Please give a clue if so.
Thanks,
Rajesh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-10-04 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 3:58 V. Rajesh
2003-10-04 5:29 ` David S. Miller
2003-10-04 5:40 ` Andrew Morton
2003-10-04 6:31 ` Rajesh Venkatasubramanian [this message]
2003-10-04 6:41 ` Andrew Morton
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.4.44.0310040223230.27636-100000@cello.eecs.umich.edu \
--to=vrajesh@eecs.umich.edu \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=hch@lst.de \
--cc=linux-mm@kvack.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