From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Scott Bauer <sbauer@eng.utah.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
the arch/x86 maintainers <x86@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Andy Lutomirski <luto@amacapital.net>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
wmealing@redhat.com,
Abhiram Balasubramanian <abhiram@cs.utah.edu>,
Scott Bauer <sbauer@plzdonthack.me>
Subject: [kernel-hardening] Re: [PATCH v4 1/4] SROP Mitigation: Architecture independent code for signal cookies
Date: Thu, 31 Mar 2016 17:17:53 -0500 [thread overview]
Message-ID: <87oa9ue1gu.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <CA+55aFy1nzw0amBKYD6SfS6-4tiCDfX7viUBHFEq-9Kzv_-Mtg@mail.gmail.com> (Linus Torvalds's message of "Thu, 31 Mar 2016 17:00:24 -0500")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> On Thu, Mar 31, 2016 at 3:25 PM, Eric W. Biederman
> <ebiederm@xmission.com> wrote:
>>
>> I suspect we want this to be a per-mm attribute rather than a per-thread
>> attribute.
>>
>> Otherwise you are breaking anything that uses a N-M threading model.
>> Which I suspect means that this implementation choice breaks all go
>> programs on linux.
>
> That sounds like a good point, but wouldn't it make more conceptual
> sense to make it part of "struct sighand_struct" instead?
>
> That is also shared for threads.
Good point. Given this is a signal handling feature
struct sighand_struct is the natural place to put this.
Eric
next prev parent reply other threads:[~2016-03-31 22:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 19:53 [kernel-hardening] [PATCH v4 0/4] SROP Mitigation: Sigreturn Cookies Scott Bauer
2016-03-29 19:53 ` [kernel-hardening] [PATCH v4 1/4] SROP Mitigation: Architecture independent code for signal cookies Scott Bauer
2016-03-29 23:04 ` [kernel-hardening] " Linus Torvalds
2016-03-31 20:25 ` Eric W. Biederman
2016-03-31 22:00 ` Linus Torvalds
2016-03-31 22:17 ` Eric W. Biederman [this message]
2016-03-29 19:53 ` [kernel-hardening] [PATCH v4 2/4] x86: SROP Mitigation: Implement Signal Cookies Scott Bauer
2016-03-29 19:53 ` [kernel-hardening] [PATCH v4 3/4] Sysctl: SROP Mitigation: Add Sysctl argument to disable SROP Scott Bauer
2016-03-29 19:59 ` [kernel-hardening] " Andi Kleen
2016-03-29 20:46 ` Scotty Bauer
2016-03-29 20:53 ` Andi Kleen
2016-03-29 19:53 ` [kernel-hardening] [PATCH v4 4/4] Documentation: SROP Mitigation: Add documentation for SROP cookies Scott Bauer
2016-03-29 20:12 ` [kernel-hardening] " Brian Gerst
2016-04-24 16:27 ` Pavel Machek
2016-03-29 21:29 ` [kernel-hardening] Re: [PATCH v4 0/4] SROP Mitigation: Sigreturn Cookies Andy Lutomirski
2016-03-29 21:36 ` Scotty Bauer
2016-03-29 21:38 ` Andy Lutomirski
2016-03-29 22:34 ` Linus Torvalds
2016-03-29 23:14 ` Scotty Bauer
2016-03-31 20:22 ` Eric W. Biederman
2016-04-01 12:57 ` Cyrill Gorcunov
2016-03-29 22:55 ` Daniel Micay
2016-04-24 16:14 ` Pavel Machek
2016-03-29 22:54 ` Linus Torvalds
2016-03-29 22:55 ` Linus Torvalds
2016-03-29 23:05 ` Andy Lutomirski
2016-03-29 23:11 ` Scotty Bauer
2016-03-29 23:25 ` Linus Torvalds
2016-03-29 23:34 ` Scotty Bauer
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=87oa9ue1gu.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=abhiram@cs.utah.edu \
--cc=ak@linux.intel.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=sbauer@eng.utah.edu \
--cc=sbauer@plzdonthack.me \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=wmealing@redhat.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