VFS: clarify that nonseekable_open() will never fail
PATCH 1/1 VFS: clarify that nonseekable_open() will never fail
Al, Andrew,
Could you please pick this one up (unless you disagree with it)?
Thanks!
Signature · 11 lines
Dmitry VFS: clarify that nonseekable_open() will never fail Acked-by: Arnd Bergmann <[email protected]> Acked-by: John Kacur <[email protected]> Signed-off-by: Dmitry Torokhov <[email protected]> --- fs/open.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-)
fs/open.c +3 -1
@@ -1200,7 +1200,9 @@ EXPORT_SYMBOL(generic_file_open);/* * This is used by subsystems that don't want seekable -* file descriptors +* file descriptors. The function is not supposed to ever fail, the only +* reason it returns an 'int' and not 'void' is so that it can be plugged +* directly into file_operations structure. */ int nonseekable_open (struct inode *inode,struct file *filp) {