Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
4947a1a3
Commit
4947a1a3
authored
Jul 06, 2003
by
Steve French
Committed by
Steve French
Jul 06, 2003
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix statfs failure due to invalid value for ffree
parent
bd792b17
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
2 deletions
+7
-2
fs/cifs/CHANGES
fs/cifs/CHANGES
+6
-1
fs/cifs/cifsfs.c
fs/cifs/cifsfs.c
+1
-1
No files found.
fs/cifs/CHANGES
View file @
4947a1a3
Version 0.81
------------
Finish up CIFS packet digital signing for the default
NTLM security case.
NTLM security case. This should help Windows 2003
network interoperability since it is common for
packet signing to be required now. Fix statfs (stat -f)
which recently started returning errors due to
invalid value (-1 instead of 0) being set in the
struct kstatfs f_ffiles field.
Version 0.80
-----------
...
...
fs/cifs/cifsfs.c
View file @
4947a1a3
...
...
@@ -165,7 +165,7 @@ cifs_statfs(struct super_block *sb, struct kstatfs *buf)
able to support more than this, but best to be safe
since Win2k and others can not handle very long filenames */
buf
->
f_files
=
0
;
/* undefined */
buf
->
f_ffree
=
-
1
;
/* unlimited */
buf
->
f_ffree
=
0
;
/* unlimited */
rc
=
CIFSSMBQFSInfo
(
xid
,
pTcon
,
buf
,
cifs_sb
->
local_nls
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment