Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*bug\:\s+truncate\s+to\s+zero\s+\+\s+setuid\s*$/: 16 ]

Total 16 documents matching your query.

1. Re: bug: truncate to zero + setuid (score: 1)
Author: Timothy Shimmin <tes@xxxxxxx>
Date: Fri, 02 Nov 2007 12:11:28 +1100
Hi Roger, Roger Willcocks wrote: Timothy Shimmin wrote: I presume it was done where it was done so that the inode was locked and we were under the XFS_AT_SIZE predicate. I was just thinking of someth
/archives/xfs/2007-11/msg00006.html (17,119 bytes)

2. Re: bug: truncate to zero + setuid (score: 1)
Author: "Roger Willcocks" <roger@xxxxxxxxxxxxxxxx>
Date: Sun, 4 Nov 2007 11:59:51 -0000
Timothy Shimmin wrote: Hi Roger, ... I don't like all these inconsistencies. Take a look at the attached patch relative to the current cvs (it's a bit big to put inline). The basic problem is it's cu
/archives/xfs/2007-11/msg00033.html (9,317 bytes)

3. Re: bug: truncate to zero + setuid (score: 1)
Author: Timothy Shimmin <tes@xxxxxxx>
Date: Thu, 08 Nov 2007 14:13:22 +1100
Hi Roger, Roger Willcocks wrote: Timothy Shimmin wrote: Hi Roger, ... I don't like all these inconsistencies. Take a look at the attached patch relative to the current cvs (it's a bit big to put inli
/archives/xfs/2007-11/msg00072.html (12,728 bytes)

4. Re: bug: truncate to zero + setuid (score: 1)
Author:
Date: Fri, 02 Nov 2007 12:11:28 +1100
Hi Roger, Roger Willcocks wrote: Timothy Shimmin wrote: I presume it was done where it was done so that the inode was locked and we were under the XFS_AT_SIZE predicate. I was just thinking of someth
/archives/xfs/2007-11/msg00322.html (17,119 bytes)

5. Re: bug: truncate to zero + setuid (score: 1)
Author:
Date: Sun, 4 Nov 2007 11:59:51 -0000
Timothy Shimmin wrote: Hi Roger, ... I don't like all these inconsistencies. Take a look at the attached patch relative to the current cvs (it's a bit big to put inline). The basic problem is it's cu
/archives/xfs/2007-11/msg00349.html (9,317 bytes)

6. Re: bug: truncate to zero + setuid (score: 1)
Author:
Date: Thu, 08 Nov 2007 14:13:22 +1100
Hi Roger, Roger Willcocks wrote: Timothy Shimmin wrote: Hi Roger, ... I don't like all these inconsistencies. Take a look at the attached patch relative to the current cvs (it's a bit big to put inli
/archives/xfs/2007-11/msg00388.html (12,728 bytes)

7. bug: truncate to zero + setuid (score: 1)
Author:
Date: Sun, 28 Oct 2007 14:36:42 +0000
The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles this fine, but if the file's being truncated to zero, and the file's already empty, XFS simply igno
/archives/xfs/2007-10/msg00253.html (7,869 bytes)

8. Re: bug: truncate to zero + setuid (score: 1)
Author:
Date: Mon, 29 Oct 2007 11:54:58 +1100
Hi Roger, Roger Willcocks wrote: The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles this fine, but if the file's being truncated to zero, and the file
/archives/xfs/2007-10/msg00258.html (9,768 bytes)

9. Re: bug: truncate to zero + setuid (score: 1)
Author:
Date: Mon, 29 Oct 2007 18:56:16 +0000
Tim Shimmin wrote: Hi Roger, Roger Willcocks wrote: The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles this fine, but if the file's being truncated to
/archives/xfs/2007-10/msg00270.html (10,647 bytes)

10. Re: bug: truncate to zero + setuid (score: 1)
Author:
Date: Tue, 30 Oct 2007 15:06:06 +1100
Roger Willcocks wrote: Tim Shimmin wrote: Hi Roger, Roger Willcocks wrote: The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles this fine, but if the fi
/archives/xfs/2007-10/msg00290.html (15,032 bytes)

11. Re: bug: truncate to zero + setuid (score: 1)
Author:
Date: Tue, 30 Oct 2007 17:28:01 +0000
Timothy Shimmin wrote: Roger Willcocks wrote: Tim Shimmin wrote: Hi Roger, Roger Willcocks wrote: The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles t
/archives/xfs/2007-10/msg00297.html (17,802 bytes)

12. bug: truncate to zero + setuid (score: 1)
Author: >
Date: Sun, 28 Oct 2007 14:36:42 +0000
The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles this fine, but if the file's being truncated to zero, and the file's already empty, XFS simply igno
/archives/xfs/2007-10/msg00580.html (7,869 bytes)

13. Re: bug: truncate to zero + setuid (score: 1)
Author: >
Date: Mon, 29 Oct 2007 11:54:58 +1100
Hi Roger, Roger Willcocks wrote: The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles this fine, but if the file's being truncated to zero, and the file
/archives/xfs/2007-10/msg00585.html (9,768 bytes)

14. Re: bug: truncate to zero + setuid (score: 1)
Author: >
Date: Mon, 29 Oct 2007 18:56:16 +0000
Tim Shimmin wrote: Hi Roger, Roger Willcocks wrote: The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles this fine, but if the file's being truncated to
/archives/xfs/2007-10/msg00597.html (10,647 bytes)

15. Re: bug: truncate to zero + setuid (score: 1)
Author: >
Date: Tue, 30 Oct 2007 15:06:06 +1100
Roger Willcocks wrote: Tim Shimmin wrote: Hi Roger, Roger Willcocks wrote: The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles this fine, but if the fi
/archives/xfs/2007-10/msg00617.html (15,032 bytes)

16. Re: bug: truncate to zero + setuid (score: 1)
Author: >
Date: Tue, 30 Oct 2007 17:28:01 +0000
Timothy Shimmin wrote: Roger Willcocks wrote: Tim Shimmin wrote: Hi Roger, Roger Willcocks wrote: The nfsv3 setattr call permits a simultaneous truncate + setuid/gid operation. Normally XFS handles t
/archives/xfs/2007-10/msg00624.html (17,802 bytes)


This search system is powered by Namazu