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
Kirill Smelkov
linux
Commits
72bd6173
Commit
72bd6173
authored
Nov 04, 2002
by
Alan Cox
Committed by
Dave Jones
Nov 04, 2002
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[PATCH] NOMMU update for fs/locks.c
Since we don't have mandatory mmap lock files we can lose this chunk
parent
9da07cd3
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
0 deletions
+2
-0
fs/locks.c
fs/locks.c
+2
-0
No files found.
fs/locks.c
View file @
72bd6173
...
@@ -1401,6 +1401,7 @@ int fcntl_setlk(struct file *filp, unsigned int cmd, struct flock *l)
...
@@ -1401,6 +1401,7 @@ int fcntl_setlk(struct file *filp, unsigned int cmd, struct flock *l)
inode
=
filp
->
f_dentry
->
d_inode
;
inode
=
filp
->
f_dentry
->
d_inode
;
#ifdef CONFIG_MMU
/* Don't allow mandatory locks on files that may be memory mapped
/* Don't allow mandatory locks on files that may be memory mapped
* and shared.
* and shared.
*/
*/
...
@@ -1413,6 +1414,7 @@ int fcntl_setlk(struct file *filp, unsigned int cmd, struct flock *l)
...
@@ -1413,6 +1414,7 @@ int fcntl_setlk(struct file *filp, unsigned int cmd, struct flock *l)
goto
out
;
goto
out
;
}
}
}
}
#endif
error
=
flock_to_posix_lock
(
filp
,
file_lock
,
&
flock
);
error
=
flock_to_posix_lock
(
filp
,
file_lock
,
&
flock
);
if
(
error
)
if
(
error
)
...
...
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