diff options
| author | Alexander Bluhm <bluhm@cvs.openbsd.org> | 2016-03-27 11:39:38 +0000 |
|---|---|---|
| committer | Alexander Bluhm <bluhm@cvs.openbsd.org> | 2016-03-27 11:39:38 +0000 |
| commit | b84b61b7ae2a04b2bf8baf435e862aefad8358e9 (patch) | |
| tree | 4a11186029a4164181c652e019bfcdb5e0c4e1ca /sys/miscfs | |
| parent | 3bec36070f359db69a5dbfe04ba988b93c7dc45c (diff) | |
When pulling and unmounting an umass USB stick, the file system
could end up in an inconsistent state. The fstype dependent
mp->mnt_data was NULL, but the general mp was still listed as a
valid mount point. Next access to the file system would crash with
a NULL pointer dereference.
If closing the device fails, the mount point must go away anyway.
There is nothing we can do about it. Remove the workaround for the
EIO error in the general unmount code, but do not generate any error
in the file system specific unmount functions.
OK natano@ beck@
Diffstat (limited to 'sys/miscfs')
| -rw-r--r-- | sys/miscfs/fuse/fuse_vfsops.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/miscfs/fuse/fuse_vfsops.c b/sys/miscfs/fuse/fuse_vfsops.c index dbf13782084..9f9541bbb5d 100644 --- a/sys/miscfs/fuse/fuse_vfsops.c +++ b/sys/miscfs/fuse/fuse_vfsops.c @@ -1,4 +1,4 @@ -/* $OpenBSD: fuse_vfsops.c,v 1.19 2016/03/17 18:52:31 bluhm Exp $ */ +/* $OpenBSD: fuse_vfsops.c,v 1.20 2016/03/27 11:39:37 bluhm Exp $ */ /* * Copyright (c) 2012-2013 Sylvestre Gallon <ccna.syl@gmail.com> * @@ -167,7 +167,7 @@ fusefs_unmount(struct mount *mp, int mntflags, struct proc *p) free(fmp, M_FUSEFS, 0); mp->mnt_data = NULL; - return (error); + return (0); } int |