From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: mmap/MAP_SHARED and mandatory flock
Date: Wed, 23 Jun 1999 11:12:30 -0700 (PDT) [thread overview]
Message-ID: <199906231812.LAA02787@google.engr.sgi.com> (raw)
It seems to me that the mmap/MAP_SHARED locks_verify_locked() check
and fcntl_setlk() have no synchronization. For example, a process
invoking fcntl_setlk on a IS_MANDLOCK inode can check that it has
no i_mmap vma list, then go on and sleep later before queueing a
file_lock on the inode i_flock. Subsequently, an mmaper can come
in, invoke locks_verify_locked(), see no file_lock on the inode
i_flock, and succeed. The file locker can then wake up and also
return success.
Am I missing some synchronization lock/algorithm?
Kanoj
kanoj@engr.sgi.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
reply other threads:[~1999-06-23 18:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199906231812.LAA02787@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=linux-kernel@vger.rutgers.edu \
--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