public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>,
	GNU C Library <libc-alpha@sourceware.org>
Cc: nd@arm.com, Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
	Joseph Myers <joseph@codesourcery.com>,
	Romain Naour <romain.naour@gmail.com>
Subject: Re: [PATCH] aarch64: Revert the change of the __reserved member of mcontext_t
Date: Fri, 26 Jan 2018 17:07:00 -0000	[thread overview]
Message-ID: <0acca6b1-6c93-991d-7228-7313a00e4120@redhat.com> (raw)
In-Reply-To: <2a9288a1-45b4-0648-7d5e-cd7be4e8957b@arm.com>

On 01/26/2018 04:02 PM, Szabolcs Nagy wrote:
> On 24/01/18 11:55, Szabolcs Nagy wrote:
>> On 23/01/18 15:16, Florian Weimer wrote:
>>> On 01/23/2018 03:35 PM, Szabolcs Nagy wrote:
>>>> The uc_mcontext.__reserved member of ucontext_t is a user visible API,
>>>> that should not be changed, because this is the only way to access cpu
>>>> states of various extensions of linux asm/sigcontext.h, it does not
>>>> violate namespace rules either, so revert this part of the commit
>>>>
>>>> commit 4fa9b3bfe6759c82beb4b043a54a3598ca467289
>>>> Commit:     Joseph Myers<joseph@codesourcery.com>
>>>>
>>>>       Fix mcontext_t sigcontext namespace (bug 21457).
>>>>
>>>> (In principle the user can type cast &uc_mcontext to struct sigcontext*
>>>> to use the linux sigcontext fields, but that's not the existing 
>>>> practice
>>>> since mcontext_t used to be a typedef of struct sigcontext.)
>>>>
>>>> I plan to commit this soon for 2.27 and backport it to 2.26 if there 
>>>> are
>>>> no comments.
>>>
>>> I think this is the right thing to do, but unfortunately, this 
>>> back-and-forth is a bit painful.
>>>
>>
>> ok, i opened bug 22742 because it's a user visible change.
>>
>> committed now on 2.27 (will backport it in a day or two).
>>
> 
> the problematic commit is not present in 2.26, so
> this is not a 2.26 regression, i'm not sure how i
> missed that (i checked the git log of 2.26 branch
> several times).
> 
> so there is no user visible api break, sorry for the noise.

Right, my mistake.  Thanks for fixing master!

Florian

      reply	other threads:[~2018-01-26 15:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 14:35 Szabolcs Nagy
2018-01-23 15:17 ` Florian Weimer
2018-01-24 11:56   ` Szabolcs Nagy
2018-01-24 21:36     ` Romain Naour
2018-01-26 17:07     ` Szabolcs Nagy
2018-01-26 17:07       ` Florian Weimer [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=0acca6b1-6c93-991d-7228-7313a00e4120@redhat.com \
    --to=fweimer@redhat.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nd@arm.com \
    --cc=romain.naour@gmail.com \
    --cc=szabolcs.nagy@arm.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).