public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Jeremy Drake <cygwin@jdrake.com>
Cc: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Add support for high-entropy-va flag to peflags.
Date: Mon, 17 May 2021 12:54:28 +0200	[thread overview]
Message-ID: <YKJLZE/QFQotdkQw@calimero.vinschen.de> (raw)
In-Reply-To: <alpine.WNT.2.22.394.2105151214260.7536@persephone>

Hi Jeremy,

On May 15 12:17, Jeremy Drake via Cygwin-patches wrote:
> This allows for setting, clearing, and displaying the value of the "high
> entropy va" dll characteristics flag.
> 
> Signed-off-by: Jeremy Drake <github@jdrake.com>
> ---
> I'm not sure this is the right list for this...

It's not, but given the low traffic, never mind that for this patch.

Thanks for the patch, but I have two nits:

- The patch doesn't apply cleanly with `git am'.  Please check again.

- I would prefer a massively reduced patch size, by *not* changing
  indentation on otherwise unaffected lines.

  I.e., ignore the problem here:

       {"dynamicbase",  optional_argument, NULL, 'd'},
    +  {"high-entropy-va", optional_argument, NULL, 'e'},

  ...and just add 

     "  -d, --dynamicbase  [BOOL]   Image base address may be relocated using\n"
    +"  -e,
    +   --high-entropy-va  [BOOL]   Image is compatible with 64-bit address space\n"
    +"                              layout randomization (ASLR).\n"

With that change I'll apply it and release a new version of rebase soon.

Oh and, btw., there's some problem with DMARC munging with your email
address.  Would you mind to attach the git patch instead of inlining
it?  I won't accidentally forget to fix your email address in the log
message then :-P


Thanks,
Corinna

  reply	other threads:[~2021-05-17 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 19:17 Jeremy Drake
2021-05-17 10:54 ` Corinna Vinschen [this message]
2021-05-17 19:15   ` Jeremy Drake
2021-05-18  7:59     ` 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=YKJLZE/QFQotdkQw@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin-patches@cygwin.com \
    --cc=cygwin@jdrake.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).