X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 2 Mar 2011 12:11:19 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 1.7.8-1 ls -l /proc/sys/Device causes system reset Message-ID: <20110302111119.GJ22240@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <669347 DOT 40317 DOT qm AT web161713 DOT mail DOT bf1 DOT yahoo DOT com> <20110302084059 DOT GA31235 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mar 2 04:23, Timothy Coalson wrote: > On Wed, Mar 2, 2011 at 2:40 AM, Corinna Vinschen >
wrote: > > On Mar  1 16:41, Tim Coalson wrote: > >> I have found two culprits so far, SSHDRV65 and SSHDRV79.  They seem to be > >> drivers related to CD copy protection software in windows. > > > > I *really* start to hate Windows XP. > > > > But I can't reproduce this, neither on XP nor on W7.  Maybe because > > I don't have these SSHDRVxx devices. > > > > What puzzles me a bit is this:  The core of the functionality is in > > a method called fhandler_procsys::exists().  This method is called > > even for a simple ls which does not stat.  The underlying stat method > > fhandler_procsys::fstat() also just calls the exists() method and then > > fills the stat buffer. > > > > Hmm... > > > > There is one difference.  If exists() is called from fstat() then > > there's an additional call to fetch the ACL from the device entry. > > That's the only additional system call in this scenario. > > > > Can you please test something for me? > > > > Fetch the WinObj tool from sysinternals: > > http://technet.microsoft.com/en-us/sysinternals/bb896657 > > > > Install it and start it.  In WinObj, open the Device directory and > > search for the SSHDRV65 and SSHDRV79 entries.  Right-click on them and > > open the Properties dialog.  Then switch to the "Security" tab. > > Does it work?  Does it show something useful or a kind of error message? > > > > > > Corinna > > > > I have switched to a different email so that I can reply properly. > > Using the tool mentioned, both of the problem devices' properties > dialogs appear to be functional.  [...] If I send you a link to a test Cygwin DLL via private email, would you mind to test it? 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