This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: sshd crashing


On Jul 31 15:59, A Lichner wrote:
> 
> Thanks Corinna. The fix works.
> Ales
> 
> 
> Corinna Vinschen-2 wrote:
> > 
> > On Jul 31 14:28, Corinna Vinschen wrote:
> >> On Jul 30 17:49, AleÅ wrote:
> >> > 
> >> > Hello,
> >> > 
> >> > I can confirm the issue. It's occurring after upgrade to 1.7.16 and
> >> seems to
> >> > be limited to VMWare guests in my case. Any write attempt within the
> >> /etc
> >> > directory causes sshd to crash. Other directories are fine.
> >> > 
> >> > uname -a before upgrade (sshd doens't crash):
> >> > CYGWIN_NT-6.0-WOW64 dbs6 1.7.15(0.260/5/3) 2012-05-09 10:25 i686 Cygwin
> >> > and after upgrade (sshd crashes):
> >> > CyGWIN_NT-6.0-WOW64 dbs6 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin
> >> > 
> >> > 
> >> > cygrunsrv -S sshd
> >> > ssh localhost
> >> > $ touch /etc/x
> >> > Connection to localhost closed by remote host.
> >> > Connection to localhost closed.
> >> > 
> >> > 
> >> > A familiar message appears in the event log:
> >> > service sshd failed: signal 11 raised 
> >> > 
> >> > The /etc/x file gets created in the example above. If running vim
> >> /etc/x
> >> > instead, the  .x.swp file gets also created and a vim-nox.exe process
> >> keeps
> >> > on living, taking all CPU resources till it's killed.
> >> > 
> >> > I have reproduced this on over ten machines running MS Server 2003 and
> >> 2008,
> >> > all VMware guests.
> >> 
> >> I can reproduce this as well.  I also found the patch which introduced
> >> the problem, but it's not clear yet, why.  Stay tuned.
> > 
> > I've just applied a patch to fix this problem.  It seems this is a long
> > standing bug which could result in random stack corruption after changing
> > or adding any file to /etc.  I'm just generating a developer snapshot.
> > Please test the today's snapshot from http://cygwin.com/snapshots/
> > Just replacing /bin/cygwin1.dll with the snapshot DLL is sufficient.

Thanks to you and Pawel for your feedback.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]