From: Florian Weimer <fweimer@redhat.com> To: Ram Pai <linuxram@us.ibm.com> Cc: Dave Hansen <dave.hansen@intel.com>, linux-mm <linux-mm@kvack.org>, x86@kernel.org, linux-arch <linux-arch@vger.kernel.org>, linux-x86_64@vger.kernel.org, Linux API <linux-api@vger.kernel.org> Subject: Re: pkeys: Support setting access rights for signal handlers Date: Mon, 18 Dec 2017 12:00:30 +0100 [thread overview] Message-ID: <7ab875c5-dc7c-b36e-8612-3d4aaf86a15c@redhat.com> (raw) In-Reply-To: <20171216172026.GC5461@ram.oc3035372033.ibm.com> On 12/16/2017 06:20 PM, Ram Pai wrote: > Ok. Sounds like I do not have much to do. My patches in its current form > will continue to work and provide the semantics you envision. Thanks for confirming. >> I'm open to a different way towards conveying this information to >> userspace. I don't want to probe for the behavior by sending a >> signal because that is quite involved and would also be visible in >> debuggers, confusing programmers. > I am fine with your proposal. So how can we move this forward? Should I submit a single new patch with the new flag with a more appropriate name (PKEY_ALLOC_SIGNALINHERIT comes to my mind) and the signal inheritance change? Dave, do you still want to wait for feedback from the x86 maintainer regarding a general interface? Is this really feasible without detailed knowledge of the XSAVE output structure? Otherwise, there probably isn't a way around code which explicitly copies the bits we want to preserve from the interrupted CPU context to the signal handler context. Thanks, Florian
WARNING: multiple messages have this Message-ID (diff)
From: Florian Weimer <fweimer@redhat.com> To: Ram Pai <linuxram@us.ibm.com> Cc: Dave Hansen <dave.hansen@intel.com>, linux-mm <linux-mm@kvack.org>, x86@kernel.org, linux-arch <linux-arch@vger.kernel.org>, linux-x86_64@vger.kernel.org, Linux API <linux-api@vger.kernel.org> Subject: Re: pkeys: Support setting access rights for signal handlers Date: Mon, 18 Dec 2017 12:00:30 +0100 [thread overview] Message-ID: <7ab875c5-dc7c-b36e-8612-3d4aaf86a15c@redhat.com> (raw) In-Reply-To: <20171216172026.GC5461@ram.oc3035372033.ibm.com> On 12/16/2017 06:20 PM, Ram Pai wrote: > Ok. Sounds like I do not have much to do. My patches in its current form > will continue to work and provide the semantics you envision. Thanks for confirming. >> I'm open to a different way towards conveying this information to >> userspace. I don't want to probe for the behavior by sending a >> signal because that is quite involved and would also be visible in >> debuggers, confusing programmers. > I am fine with your proposal. So how can we move this forward? Should I submit a single new patch with the new flag with a more appropriate name (PKEY_ALLOC_SIGNALINHERIT comes to my mind) and the signal inheritance change? Dave, do you still want to wait for feedback from the x86 maintainer regarding a general interface? Is this really feasible without detailed knowledge of the XSAVE output structure? Otherwise, there probably isn't a way around code which explicitly copies the bits we want to preserve from the interrupted CPU context to the signal handler context. Thanks, Florian -- 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:[~2017-12-18 11:00 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-09 21:16 pkeys: Support setting access rights for signal handlers Florian Weimer [not found] ` <5fee976a-42d4-d469-7058-b78ad8897219-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> 2017-12-10 0:17 ` Dave Hansen 2017-12-10 0:17 ` Dave Hansen 2017-12-10 0:17 ` Dave Hansen 2017-12-10 6:42 ` Florian Weimer 2017-12-10 6:42 ` Florian Weimer 2017-12-11 16:13 ` Dave Hansen 2017-12-11 16:13 ` Dave Hansen 2017-12-12 23:13 ` Ram Pai 2017-12-12 23:13 ` Ram Pai 2017-12-13 2:14 ` Florian Weimer 2017-12-13 2:14 ` Florian Weimer 2017-12-13 11:35 ` Ram Pai 2017-12-13 11:35 ` Ram Pai [not found] ` <20171213113544.GG5460-LOE2q6NSToAxGrZ80giIafUQ3DHhIser@public.gmane.org> 2017-12-13 15:08 ` Florian Weimer 2017-12-13 15:08 ` Florian Weimer 2017-12-13 15:08 ` Florian Weimer 2017-12-13 15:22 ` Dave Hansen 2017-12-13 15:22 ` Dave Hansen 2017-12-13 15:40 ` Florian Weimer 2017-12-13 15:40 ` Florian Weimer 2017-12-14 0:17 ` Ram Pai 2017-12-14 0:17 ` Ram Pai 2017-12-14 11:21 ` Florian Weimer 2017-12-16 15:09 ` Ram Pai 2017-12-16 15:09 ` Ram Pai 2017-12-16 15:25 ` Florian Weimer 2017-12-16 15:25 ` Florian Weimer [not found] ` <2eba29f4-804d-b211-1293-52a567739cad-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> 2017-12-16 17:20 ` Ram Pai 2017-12-16 17:20 ` Ram Pai 2017-12-16 17:20 ` Ram Pai 2017-12-18 11:00 ` Florian Weimer [this message] 2017-12-18 11:00 ` Florian Weimer
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=7ab875c5-dc7c-b36e-8612-3d4aaf86a15c@redhat.com \ --to=fweimer@redhat.com \ --cc=dave.hansen@intel.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=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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.