Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+Check\s+for\s+immutable\s+flag\s+in\s+fallocate\s+path\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+Check\s+for\s+immutable\s+flag\s+in\s+fallocate\s+path\s*$/: 7 ]

Total 7 documents matching your query.

1. [PATCH] Check for immutable flag in fallocate path (score: 1): Author: Marco Stornelli <marco.stornelli@xxxxxxxxx>; Date: Mon, 21 Feb 2011 09:26:32 +0100; 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, meanwhil; /archives/xfs/2011-02/msg00190.html (10,281 bytes)
2. Re: [PATCH] Check for immutable flag in fallocate path (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Mon, 21 Feb 2011 07:46:35 -0500; Please add the check in fs/open.c:do_fallocate() so that it covers all filesystems.; /archives/xfs/2011-02/msg00191.html (8,434 bytes)
3. Re: [PATCH] Check for immutable flag in fallocate path (score: 1): Author: Marco Stornelli <marco.stornelli@xxxxxxxxx>; Date: Mon, 21 Feb 2011 17:50:21 +0100; 2011/2/21 Christoph Hellwig <hch@xxxxxxxxxxxxx>: The check should be done after the fs got the inode mutex lock. Marco; /archives/xfs/2011-02/msg00197.html (9,784 bytes)
4. Re: [PATCH] Check for immutable flag in fallocate path (score: 1): Author: Marco Stornelli <marco.stornelli@xxxxxxxxx>; Date: Sat, 26 Feb 2011 15:59:27 +0100; Il 21/02/2011 09:26, Marco Stornelli ha scritto: no comments?; /archives/xfs/2011-02/msg00289.html (9,391 bytes)
5. Re: [PATCH] Check for immutable flag in fallocate path (score: 1): Author: "Ted Ts'o" <tytso@xxxxxxx>; Date: Sun, 27 Feb 2011 17:49:40 -0500; Why? None of the other places which check the IMMUTABLE flag do so under the inode mutex lock. Yes, it's true that we're not properly doing proper locking when updating i_flags from the ioctl (this i; /archives/xfs/2011-02/msg00290.html (11,155 bytes)
6. Re: [PATCH] Check for immutable flag in fallocate path (score: 1): Author: Marco Stornelli <marco.stornelli@xxxxxxxxx>; Date: Mon, 28 Feb 2011 08:53:31 +0100; 2011/2/27 Ted Ts'o <tytso@xxxxxxx>: I was thinking to the possible race with setattr callback. Marco; /archives/xfs/2011-02/msg00291.html (12,419 bytes)
7. Re: [PATCH] Check for immutable flag in fallocate path (score: 1): Author: Marco Stornelli <marco.stornelli@xxxxxxxxx>; Date: Wed, 02 Mar 2011 09:19:54 +0100; Il 27/02/2011 23:49, Ted Ts'o ha scritto: I add to my previous response an other point: IMHO each fs should check for it because after the inclusion of punch hole patch, the fs can/cannot check for t; /archives/xfs/2011-03/msg00019.html (10,857 bytes)

Current List: 1 - 7
Page: [1]