From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthew Wilcox <willy@debian.org>
Subject: aio_fsync
Date: Fri, 18 Jul 2003 19:33:36 +0100
Sender: owner-linux-aio@kvack.org
Message-ID: <20030718183336.GW23808@parcelfarce.linux.theplanet.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org
Return-path: <owner-linux-aio@kvack.org>
To: linux-aio@kvack.org
Content-Disposition: inline
List-Id: linux-fsdevel.vger.kernel.org

i'm updating the Documentation/filesystem/Locking document.
i notice that sys_fsync() takes the i_sem before calling ->fsync, but
io_submit_one() does not take i_sem before calling ->aio_fsync.

is this intentional?  do we not need to protect against concurrent
writers as sys_fsync does?

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org.  For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>