From: Marco Stornelli Subject: Re: [PATCH] Check for immutable flag in fallocate path Date: Sat, 26 Feb 2011 15:59:27 +0100 Message-ID: <4D69154F.8090000@gmail.com> References: <4D6221B8.9040303@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org, cluster-devel@redhat.com, xfs@oss.sgi.com, Linux FS Devel To: Linux Kernel Return-path: Received: from mail-ww0-f42.google.com ([74.125.82.42]:52422 "EHLO mail-ww0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751367Ab1BZPE2 (ORCPT ); Sat, 26 Feb 2011 10:04:28 -0500 In-Reply-To: <4D6221B8.9040303@gmail.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: Il 21/02/2011 09:26, Marco Stornelli ha scritto: > From: Marco Stornelli > > All fs must check for the immutable flag in their fallocate callback. > It's possible to have a race condition in this scenario: an application > open a file in read/write and it does something, meanwhile root set the > immutable flag on the file, the application at that point can call > fallocate with success. Only Ocfs2 check for the immutable flag at the > moment. > > Signed-off-by: Marco Stornelli no comments?