X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=1.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20110302111119.GJ22240@calimero.vinschen.de> 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> <20110302111119 DOT GJ22240 AT calimero DOT vinschen DOT de> Date: Wed, 2 Mar 2011 05:13:55 -0600 Message-ID: Subject: Re: 1.7.8-1 ls -l /proc/sys/Device causes system reset From: Timothy Coalson To: cygwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes 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 Wed, Mar 2, 2011 at 5:11 AM, Corinna Vinschen
wrote: > On Mar =A02 04:23, Timothy Coalson wrote: >> On Wed, Mar 2, 2011 at 2:40 AM, Corinna Vinschen >>
wrote: >> > On Mar =A01 16:41, Tim Coalson wrote: >> >> I have found two culprits so far, SSHDRV65 and SSHDRV79. =A0They 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. =A0Maybe because >> > I don't have these SSHDRVxx devices. >> > >> > What puzzles me a bit is this: =A0The core of the functionality is in >> > a method called fhandler_procsys::exists(). =A0This method is called >> > even for a simple ls which does not stat. =A0The underlying stat method >> > fhandler_procsys::fstat() also just calls the exists() method and then >> > fills the stat buffer. >> > >> > Hmm... >> > >> > There is one difference. =A0If 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. =A0In WinObj, open the Device directory and >> > search for the SSHDRV65 and SSHDRV79 entries. =A0Right-click on them a= nd >> > open the Properties dialog. =A0Then switch to the "Security" tab. >> > Does it work? =A0Does it show something useful or a kind of error mess= age? >> > >> > >> > 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. =A0[...] > > If I send you a link to a test Cygwin DLL via private email, would > you mind to test it? > > > Corinna Sure, either email should work. -- 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