From: "warren" <warren@infortrend.com.tw>
To: <linux-kernel@vger.kernel.org>
Subject: race condition on looking up inodes
Date: Mon, 9 Apr 2001 11:26:51 +0800 [thread overview]
Message-ID: <000201c0c0a4$eb5c7b10$321ea8c0@saturn> (raw)
Hi,
I had post a simillar message before.
Thanks for the replay from Albert D. Cahalan. But i found some results
confusing me.
For example, process 1 and process 2 run concurrently and execute the
following system calls.
rename("/usr/hybrid/cfg/data","/usr/mytemp/data1"); /*for process 1*/
----------------------------------------------------------------
rename("/usr/mytemp/data1","/usr/test");/* for process 2*/
----------------------------------------------------------------
It is possible that context switch happens when process 1 is look ing up
the inode for "/usr/mytemp/data1" or the inode for "/usr/hybrid/cfg/data".
It will result in diffrent behaviour for process 2 and confuses the
application.
If so,how does Linux solve?
Thanks.
Warren
next reply other threads:[~2001-04-09 3:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 3:26 warren [this message]
2001-04-09 4:39 ` Alexander Viro
2001-04-09 5:03 ` Bernd Eckenfels
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='000201c0c0a4$eb5c7b10$321ea8c0@saturn' \
--to=warren@infortrend.com.tw \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®