From: Mark Geisert <mark@maxrnd.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: Allow to set SO_PEERCRED zero (v2)
Date: Mon, 7 Dec 2020 19:25:49 -0800 [thread overview]
Message-ID: <0dffe28e-1b11-3637-ade1-c005a554ce50@maxrnd.com> (raw)
In-Reply-To: <20201207153513.GK5295@calimero.vinschen.de>
Hi Corinna,
Corinna Vinschen via Cygwin-patches wrote:
> On Dec 7 16:30, Corinna Vinschen via Cygwin-patches wrote:
>> On Dec 7 02:29, Mark Geisert wrote:
>>> The existing code errors as EINVAL any attempt to set a value for
>>> SO_PEERCRED via setsockopt() on an AF_UNIX/AF_LOCAL socket. But to
>>> enable the workaround set_no_getpeereid behavior for Python one has
>>> to be able to set SO_PEERCRED to zero. Ergo, this patch. Python has
>>> no way to specify a NULL pointer for 'optval'.
>>>
>>> This v2 of patch allows the original working (i.e., allow NULL,0 for
>>> optval,optlen to mean turn off SO_PEERCRED) in addition to the new
>>> working described above. The sense of the 'if' stmt is reversed for
>>> readability.
>>>
>>> ---
[...]
>>> --
>>> 2.29.2
>>
>> Pushed
>
> I created new developer snapshots for testing.
I didn't phrase my comment somewhere about "future snapshot TBA" as I had
intended. I just meant some future snapshot, not that I was requesting one for
this patch. But thank you very much anyway. I'll sort out with Marco whether the
Python end of the OP's issue patch should go into pythonX.X-test or pythonX.X
itself, separately. BTW The whole set of Python tests might serve to test Cygwin
in a manner we haven't seen|used yet...
Cheers,
..mark
next prev parent reply other threads:[~2020-12-08 3:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 10:29 Mark Geisert
2020-12-07 15:30 ` Corinna Vinschen
2020-12-07 15:35 ` Corinna Vinschen
2020-12-08 3:25 ` Mark Geisert [this message]
2020-12-08 9:47 ` Corinna Vinschen
2020-12-08 9:53 ` 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=0dffe28e-1b11-3637-ade1-c005a554ce50@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin-patches@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).