From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Cc: Ken Brown <kbrown@cornell.edu>,
Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
Subject: Re: Fork problem with hexchat if cygserver is running
Date: Thu, 08 Aug 2019 08:57:00 -0000 [thread overview]
Message-ID: <20190808085734.GH11632@calimero.vinschen.de> (raw)
In-Reply-To: <20190808082440.GF11632@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 2739 bytes --]
On Aug 8 10:24, Corinna Vinschen wrote:
> On Aug 8 09:27, Michael Haubenwallner wrote:
> > On 8/7/19 7:41 PM, Ken Brown wrote:
> > > Roughly 1 out of 3 times that I try to use hexchat, I get a fork failure:
> > > [...]
> > > 363 26064 [main] hexchat 12399 C:\cygwin64\bin\hexchat.exe: *** fatal error
> > > in forked process - fixup_shms_after_fork: NtMapViewOfSection (0x7FF4EE130000),
> > > status 0xC0000018. Terminating.
> > >
> > > [status 0xC0000018 is STATUS_CONFLICTING_ADDRESSES.]
> > >
> > > This was under cygwin-3.0.7-1. It also happens with cygwin1.dll
> > > built from the current master branch, and it also happens with
> > > cygwin-3.0.6-1. Not being familiar with this part of the Cygwin
> > > code, my first thought was to do a bisection. But I haven't yet
> > > found a good revision to start with. I will still try to do that,
> > > but in the meantime I thought I should report it.
> >
> > I doubt there is a commit that introduces this problem. Instead, this feels
> > like an address conflict with some (internal) memory allocated for some Windows
> > (or even Cygwin) object.
> > So I'd wonder if early memory reservation like is done for dynamically loaded
> > DLLs may help for SHMs as well.
>
> That sounds like a good idea for a start, but I don't think so. The
> interesting thing here is not that it fails, but that it fails with the
> above address:
>
> NtMapViewOfSection (0x7FF4EE130000)
> ^^^^^^^^^^^^^^
>
> Note that this address is a 48 bit address, starting with 0x7f.
>
> Up to the current Cygwin 3.0.7, Cygwin's mmap only uses 44 bit addresses
> below 0x0700:00000000, top-down. The reason is that older 64 bit
> Windows versions only support a 44 bit address space. Starting with
> Windows 8.1, Windows supports a 48 bit address space, and Cygwin 3.1
> will support that as well, by utilizing the address space top-down
> from 0x7000:00000000.
>
> However, the above address is beyond even that, in the middle of the
> address space utilized by Windows itself. Combine that with ASLR...
>
> Given that, my guess is that we're actually running into the
> problem that the shmat() call does not utilize the mmap address
> allocator, so the chosen address has a high probability to collide
> with Windows' own stuff.
>
> IMHO, the fix would be to make the mmap_alloc object global, so it
> can be utilized by shmat() to create more sane addresses.
>
> Does that make sense?
I've sent a preliminary (untested) patch to the cygwin-patches ML.
Can you two please review it?
Ken, can you also test it in your scenario, please?
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-08-08 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 17:41 Ken Brown
2019-08-07 18:46 ` Achim Gratz
2019-08-08 7:27 ` Michael Haubenwallner
2019-08-08 8:24 ` Corinna Vinschen
2019-08-08 8:57 ` Corinna Vinschen [this message]
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=20190808085734.GH11632@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
--cc=michael.haubenwallner@ssi-schaefer.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).