linux-kernel - Re: PROBLEM: FUSE unmount breaks serial terminal line

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <E1GEuMZ-0004uq-00@dorka.pomaz.szeredi.hu>
Date:	Sun, 20 Aug 2006 22:57:43 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	jo@...mrey.de
CC:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: FUSE unmount breaks serial terminal line

> something in FUSE breaks serial devices.  I found this issue 
> using gphotofs, don't know if any other FUSE impementation has similar
> effects.  The problem is: from the moment the FUSE filesystem is unmounted,
> a process that read()s on a serial device /dev/ttyS? gets an EOF
> returncode.  
> 
> Here is the tail of the output from "strace -tt cat /dev/ttyS0" when the
> FUSE fs was unmounted:
> 
> 19:41:46.513143 open("/dev/ttyS0", O_RDONLY|O_LARGEFILE) = 3
> 19:41:46.513373 fstat64(3, {st_mode=S_IFCHR|0660, st_rdev=makedev(4, 64), ...}) = 0
> 19:41:46.513552 read(3, "", 4096)       = 0
> 19:42:49.854367 close(3)                = 0
> 19:42:49.860663 close(1)                = 0
> 19:42:49.860793 exit_group(0)           = ?
> 
> Found this on x86 with kernels 2.6.16 and 2.6.17.
> 
> Any ideas?

Likely a userspace issue.  Can you please attach a strace (strace -f
-p `pidof gphotofs`) to the gphotofs process just before doing the
unmount?

Thanks,
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/