From: Ingo Molnar <mingo@kernel.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-mm <linux-mm@kvack.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-x86_64@vger.kernel.org,
Linux API <linux-api@vger.kernel.org>,
x86@kernel.org, Dave Hansen <dave.hansen@intel.com>,
Ram Pai <linuxram@us.ibm.com>
Subject: Re: [REGRESSION] testing/selftests/x86/ pkeys build failures
Date: Tue, 16 Jan 2018 03:37:59 +0100 [thread overview]
Message-ID: <20180116023759.4xpgkc53qfbtmemb@gmail.com> (raw)
In-Reply-To: <063ba398-88e6-8650-2905-c378ee1fb8b2@redhat.com>
* Florian Weimer <fweimer@redhat.com> wrote:
> On 01/12/2018 01:55 PM, Ingo Molnar wrote:
> >
> > * Florian Weimer <fweimer@redhat.com> wrote:
> >
> > > This patch is based on the previous discussion (pkeys: Support setting
> > > access rights for signal handlers):
> > >
> > > https://marc.info/?t=151285426000001
> > >
> > > It aligns the signal semantics of the x86 implementation with the upcoming
> > > POWER implementation, and defines a new flag, so that applications can
> > > detect which semantics the kernel uses.
> > >
> > > A change in this area is needed to make memory protection keys usable for
> > > protecting the GOT in the dynamic linker.
> > >
> > > (Feel free to replace the trigraphs in the commit message before committing,
> > > or to remove the program altogether.)
> >
> > Could you please send patches not as MIME attachments?
>
> My mail infrastructure corrupts patches not sent as attachments, sorry.
Your headers suggest the following mail client:
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
Thunderbird/52.5.0
Have you seen the suggestions in Documentation/process/email-clients.rst, which
lists a handful of Thunderbird tips:
Thunderbird (GUI)
*****************
Thunderbird is an Outlook clone that likes to mangle text, but there are ways
to coerce it into behaving.
?
> > Also, the protection keys testcase first need to be fixed, before we complicate
> > them - for example on a pretty regular Ubuntu x86-64 installation they fail to
> > build with the build errors attached further below.
>
> I can fix things up so that they build on Fedora 26, Debian stretch, and Red
> Hat Enterprise Linux 7. Would that be sufficient?
Yeah, I think so.
> Fedora 23 is out of support and I'd prefer not invest any work into it.
>
> Note that I find it strange to make this a precondition for even looking at
> the patch.
I wanted to try the patch to give review feedback, but found these annoyances.
It's customary to make new features dependent on the cleanliness of the underlying
code.
Thanks,
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-01-16 2:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 12:31 [PATCH] mm, x86: pkeys: Introduce PKEY_ALLOC_SIGNALINHERIT and change signal semantics Florian Weimer
2018-01-12 12:55 ` [REGRESSION] testing/selftests/x86/ pkeys build failures (was: Re: [PATCH] mm, x86: pkeys: Introduce PKEY_ALLOC_SIGNALINHERIT and change signal semantics) Ingo Molnar
2018-01-12 13:15 ` [REGRESSION] testing/selftests/x86/ pkeys build failures Florian Weimer
2018-01-16 2:37 ` Ingo Molnar [this message]
2018-01-12 14:14 ` [REGRESSION] testing/selftests/x86/ pkeys build failures (was: Re: [PATCH] mm, x86: pkeys: Introduce PKEY_ALLOC_SIGNALINHERIT and change signal semantics) Ingo Molnar
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=20180116023759.4xpgkc53qfbtmemb@gmail.com \
--to=mingo@kernel.org \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fweimer@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-x86_64@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=shuahkh@osg.samsung.com \
--cc=x86@kernel.org \
/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