From: Cedric Blancher <cedric.blancher@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Kernel stack trace for Winows 10 blue screen when running Cygwin?
Date: Mon, 7 Aug 2023 12:43:01 +0200 [thread overview]
Message-ID: <CALXu0UfsYo=CMpApdVWF5S3Vw5pwMbB70o0UJ9tdHDE05gHGOw@mail.gmail.com> (raw)
In-Reply-To: <ZNC/jK1A7iolJku4@calimero.vinschen.de>
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
next prev parent reply other threads:[~2023-08-07 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALXu0UfBK0+tYO_-3rgvZhpmKh8z4aVqMJMZ2=LfFmuJ1Vsmzw@mail.gmail.com>
2023-08-07 9:29 ` Fwd: " Cedric Blancher
2023-08-07 9:55 ` Corinna Vinschen
2023-08-07 10:43 ` Cedric Blancher [this message]
2023-08-07 11:23 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALXu0UfsYo=CMpApdVWF5S3Vw5pwMbB70o0UJ9tdHDE05gHGOw@mail.gmail.com' \
--to=cedric.blancher@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).