[kernel] r4818 - patch-tracking

[Simon Horman]

Author: horms
Date: Mon Nov 14 02:42:30 2005
New Revision: 4818

Added:
   patch-tracking/nfsd-lease-leak.patch
      - copied, changed from r4817, patch-tracking/00example
Log:
Added nfsd-lease-leak.patch

Copied: patch-tracking/nfsd-lease-leak.patch (from r4817, patch-tracking/00example)
==============================================================================
--- patch-tracking/00example	(original)
+++ patch-tracking/nfsd-lease-leak.patch	Mon Nov 14 02:42:30 2005
@@ -1,32 +1,34 @@
 ## Lines beginning with '##' are just for this example - they shouldn't be
 ## transferred to patch track files
 ## A list of valid fields for patch description files, with examples
-Candidate: ##NEEDED## | CAN/CVE-XXXX-XXXX | N/A
+Candidate: NEEDED
 ## See: http://cve.mitre.org/cve/refs/refkey.html for mitre's reference key to
 ## when adding to the References field
 References:
- CONFIRM:##URL##
- MISC:##URL## 
+ CONFIRM: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=dc15ae14e97ee9d5ed740cbb0b94996076d8b37e
+          http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f3a9388e4ebea57583272007311fffa26ebbb305
+ MISC:
 Description: 
- Summary of the issue
+ [PATCH] VFS: Fix memory leak with file leases
  .
- Might be used for requesting a CVE, or included in a DSA
+ http://linux.bkbits.net:8080/linux-2.6/diffs/fs/locks.c@1.70??nav=index.htm
++introduced a pretty nasty memory leak in the lease code. When freeing
+ the lease, the code in locks_delete_lock() will correctly clean up
+ the fasync queue, but when we return to fcntl_setlease(), the freed
+ fasync entry will be reinstated.                                   
+ .
+ This patch ensures that we skip the call to fasync_helper() when we're
+ freeing up the lease.                                                 
 Notes:
- Notes for internal use by the kernel team
-Bugs: 123456, 123457
-## per-tree status.
-##  pending: fix has been committed to svn
-##  released: we've cut a version with this fix in it
-##  needed: bug is applicable to this tree and needs a fix
-##  An empty value means that someone needs to determine the relevancy for this tree
-## 
-##
-## status maybe followed by a version string in ()'s, and/or a patchname in []'s
-## Prerequisite patches maybe listed in [] as well, even though they may not be
-## directly part of the fix.
-upstream: released (2.6.12, 2.4.29-rc3), pending (2.6.11.3)
-2.6.13: pending
-2.6.12: pending (2.6.12-9)
-2.6.8-sarge-security: released (2.6.8-16sarge1) [patchname.patch, prerequisite.dpatch, prerequisite2.dpatch]
-2.4.27-sarge-security: needed
+ There are two patches, one from J. Bruce Fields and
+ Trond Myklebust and a subsequent one from Chris Wright. 
+ They are dc15ae14e97ee9d5ed740cbb0b94996076d8b37e and
+ f3a9388e4ebea57583272007311fffa26ebbb305 in  Linus' git tree.
+ And they are both needed.
+Bugs:
+upstream: pending
+2.6.13: needed
+2.6.12: 
+2.6.8-sarge-security: 
+2.4.27-sarge-security: N/A
 2.4.27: N/A