From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin Jambor" Subject: I_LOCK description? Date: Fri, 18 Aug 2006 22:52:41 +0200 Message-ID: <9615ac9b0608181352n5608bb61m169abe24be912bd2@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from nf-out-0910.google.com ([64.233.182.191]:17346 "EHLO nf-out-0910.google.com") by vger.kernel.org with ESMTP id S932335AbWHRUwn (ORCPT ); Fri, 18 Aug 2006 16:52:43 -0400 Received: by nf-out-0910.google.com with SMTP id o25so1385566nfa for ; Fri, 18 Aug 2006 13:52:42 -0700 (PDT) To: "Linux FS Development List" Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, may I kindly request that some knowledgeable person in an altruistic mood would write a brief description of the I_LOCK bit of an inode and either send it here or even better add it to Documentation/filesystems? I have a fuzzy idea about it from reading the source but I keep on finding new uses every now and then (and forgetting about those I found long time ago). For example I realized write_inode() is called with I_LOCK locked only after I deadlocked on it :-( Thank you very much in advance, Martin