DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 126C63858D28
MIME-Version: 1.0
References: <CALXu0UfBK0+tYO_-3rgvZhpmKh8z4aVqMJMZ2=LfFmuJ1Vsmzw@mail.gmail.com>
 <CALXu0UewB26V01xbNTyTRPxCwtW_iyTD-_92_9WzrJLtwX6FwA@mail.gmail.com>
 <ZNC/jK1A7iolJku4@calimero.vinschen.de>
In-Reply-To: <ZNC/jK1A7iolJku4@calimero.vinschen.de>
Date: Mon, 7 Aug 2023 12:43:01 +0200
Message-ID: <CALXu0UfsYo=CMpApdVWF5S3Vw5pwMbB70o0UJ9tdHDE05gHGOw@mail.gmail.com>
Subject: Re: Kernel stack trace for Winows 10 blue screen when running Cygwin?
To: cygwin@cygwin.com
From: Cedric Blancher via Cygwin <cygwin@cygwin.com>
Reply-To: Cedric Blancher <cedric.blancher@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On Mon, 7 Aug 2023 at 11:55, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>
> On Aug  7 11:29, Cedric Blancher via Cygwin wrote:
> > Forwarding to cygwin@cygwin.com
> >
> > Honestly I find it deeply concerning that a plain, unprivileged user
> > can Bluescreen a machine, and more so that it happens during normal
> > Cygwin usage.
>
> Same here.  Cygwin is userspace only!
>
> If any call in Cygwin can generate a bluescreen, it's a bug in the
> kernel or in the driver.  Naturally, we have neither control over the
> kernel, nor over the NTFS driver.  You might want to open a support case
> with Microsoft.

Well, a colleague is handling that. The feedback sent to her however was that:
- Cygwin is not a Windows product
- We should WSL instead
- Cygwin might make use private Windows apis
- We should run this by the "Cygwin company"

It is my turn now to provide a kernel stack trace to prove them wrong
- IF I can manage to make one. That's why I am asking for help here.

HELP!

Ced

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