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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 22 Aug 2006 20:24:41 +0200
From:	Joerg Sommrey <jo@...mrey.de>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: FUSE unmount breaks serial terminal line

On Tue, Aug 22, 2006 at 06:54:11PM +0100, Russell King wrote:
> On Tue, Aug 22, 2006 at 07:43:29PM +0200, Joerg Sommrey wrote:
> > On Tue, Aug 22, 2006 at 06:07:24PM +0200, Miklos Szeredi wrote:
> > > > Tested both gphoto2 and gtkam without any problems. There is no impact
> > > > on the serial lines.
> > > > 
> > > > NB: The *real* trouble I have is with ntpd and a reference clock
> > > > attached to /dev/ttyS1.  ntpd enters a busy loop reading ttyS1, stops
> > > > working and eats up 100% CPU.  
> > > > 
> > > > Thanks for your investigations.  Any other idea?
> > > 
> > > Try 'killall -9 gphotofs' and then the 'fusermount -u'.
> > > 
> > > Does that have the same effect?  If so, after which does the serial
> > > line die?
> > 
> > Here are the results and another insight:  only the first serial device
> > open for reading is affected.  I.e. if ttyS0 is open for reading,
> > ttyS1 doesn't break.  If ttyS0 is not open, then ttyS1 breaks.  This
> > happens when gphotofs gets killed (or with fusermount -u without
> > killing).
> 
> Have you checked to see what files gphotofs has open?  (Check in
> /proc/<pid>/fd/).
> 

Sure I did check this.  No ttyS? there.
Thanks anyway!

-jo

-- 
-rw-r--r-- 1 jo users 62 2006-08-22 19:05 /home/jo/.signature
-
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/

Powered by blists - more mailing lists