The patch didn't apply without ignoring whitespace. Here it is again
with tabs intact.
--------------------- Cut Here ----------------------------------------
The recent change to locks_remove_flock code in fs/locks.c changes how
byte range locks are removed from closing files, which shows up a bug in
cifs. The assumption in the cifs code was that the close call sent to
the server would remove any pending locks on the server on this file,
but that is no longer safe as the fs/locks.c code on the client wants
unlock of 0 to PATH_MAX to remove all locks (at least from this client,
it is not possible AFAIK to remove all locks from other clients made to
the server copy of the file). Note that cifs locks are different from
posix locks - and it is not possible to map posix locks perfectly on the
wire yet, due to restrictions of the cifs network protocol, even to
Samba without adding a new request type to the network protocol (which
we plan to do for Samba 3.0.21 within a few months), but the local
client will have the correct, posix view, of the lock in most cases.
The correct fix for cifs for this would involve a bigger change than I
would like to do this late in the 2.6.13-rc cycle - and would involve
cifs keeping track of all unmerged (uncoalesced) byte range locks for
each remote inode and scanning that list to remove locks that intersect
or fall wholly within the range - locks that intersect may have to be
reaquired with the smaller, remaining range.
The immediate need though is for the following fix to get into 2.6.13 to
at least avoid the oops in the vfs.
[CIFS] Fix oops in fs/locks.c on close of file with pending locks
Signed-off-by: Steve French <[email protected]>
Signed-off-by: Dave Kleikamp <[email protected]>
diff -Naur linux-2.6.13-rc7/fs/cifs/file.c linux/fs/cifs/file.c
--- linux-2.6.13-rc7/fs/cifs/file.c 2005-06-17 14:48:29.000000000 -0500
+++ linux/fs/cifs/file.c 2005-08-26 07:40:37.000000000 -0500
@@ -643,7 +643,7 @@
netfid, length,
pfLock->fl_start, numUnlock, numLock, lockType,
wait_flag);
- if (rc == 0 && (pfLock->fl_flags & FL_POSIX))
+ if (pfLock->fl_flags & FL_POSIX)
posix_lock_file_wait(file, pfLock);
FreeXid(xid);
return rc;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |