1
0
Files
linux/fs
Jeff Layton 47c78b7f40 cifs: don't call cifs_new_fileinfo unless cifs_open succeeds
It's currently possible for cifs_open to fail after it has already
called cifs_new_fileinfo. In that situation, the new fileinfo will be
leaked as the caller doesn't call fput. That in turn leads to a busy
inodes after umount problem since the fileinfo holds an extra inode
reference now. Shuffle cifs_open around a bit so that it only calls
cifs_new_fileinfo if it's going to succeed.

Signed-off-by: Jeff Layton <jlayton@redhat.com>
Reviewed-and-Tested-by: Suresh Jayaraman <sjayaraman@suse.de>
2010-06-16 13:40:17 -04:00
..
2010-05-27 22:05:02 -04:00
2010-05-27 09:12:41 -07:00
2010-05-19 22:41:57 -04:00
2010-04-30 14:52:51 -05:00
2010-06-04 17:16:30 -04:00
2010-05-27 09:12:47 -07:00
2010-05-27 22:16:05 -04:00
2010-05-27 22:15:33 -04:00
2010-03-19 08:05:10 +01:00
2010-05-27 22:15:33 -04:00
2010-05-21 18:31:16 -04:00
2010-05-21 18:31:16 -04:00
2010-05-11 17:43:58 +02:00
2010-03-06 11:26:29 -08:00
2010-05-21 18:31:16 -04:00
2010-03-08 16:55:37 +01:00
2010-05-21 18:31:17 -04:00
2010-05-18 08:57:00 +10:00
2010-05-21 18:31:17 -04:00
2010-06-10 19:08:34 +02:00
2010-05-27 09:12:56 -07:00
2010-03-12 15:52:32 -08:00
2010-05-21 18:31:17 -04:00
2010-06-01 12:42:12 +02:00