From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org, linux-snps-arc@lists.infradead.org,
Vineet Gupta <vgupta@synopsys.com>
Subject: [REVIEW][PATCH 0/2] signal/arc: siginfo cleanups
Date: Mon, 24 Sep 2018 16:47:44 +0200 [thread overview]
Message-ID: <874lef2bqn.fsf@xmission.com> (raw)
I have been slowly cleaning up the architectues ever since I discovered
that the pattern of passing in struct siginfo is error prone, and
occassionally results in borken siginfo being sent to userspace.
What is happening on arc is pretty tame and I have compile tested
these changes, so I don't expect problems.
Still I would appreciate if people can look over the code and perhaps
test it and see if they can spot anything that has perhaps gone wrong.
appreciate it.
My intention is to merge this through my siginfo tree. If you feel it
should go through your arch tree let me know. All of the prerequisites
should have been merged several releases ago.
Eric W. Biederman (2):
signal/arc: Push siginfo generation into unhandled_exception
signal/arc: Use force_sig_fault where appropriate
arch/arc/kernel/traps.c | 22 ++++++++--------------
arch/arc/mm/fault.c | 20 +++++---------------
2 files changed, 13 insertions(+), 29 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: linux-snps-arc@lists.infradead.org
Subject: [REVIEW][PATCH 0/2] signal/arc: siginfo cleanups
Date: Mon, 24 Sep 2018 16:47:44 +0200 [thread overview]
Message-ID: <874lef2bqn.fsf@xmission.com> (raw)
I have been slowly cleaning up the architectues ever since I discovered
that the pattern of passing in struct siginfo is error prone, and
occassionally results in borken siginfo being sent to userspace.
What is happening on arc is pretty tame and I have compile tested
these changes, so I don't expect problems.
Still I would appreciate if people can look over the code and perhaps
test it and see if they can spot anything that has perhaps gone wrong.
appreciate it.
My intention is to merge this through my siginfo tree. If you feel it
should go through your arch tree let me know. All of the prerequisites
should have been merged several releases ago.
Eric W. Biederman (2):
signal/arc: Push siginfo generation into unhandled_exception
signal/arc: Use force_sig_fault where appropriate
arch/arc/kernel/traps.c | 22 ++++++++--------------
arch/arc/mm/fault.c | 20 +++++---------------
2 files changed, 13 insertions(+), 29 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: <linux-kernel@vger.kernel.org>
Cc: <linux-arch@vger.kernel.org>,
linux-snps-arc@lists.infradead.org,
Vineet Gupta <vgupta@synopsys.com>
Subject: [REVIEW][PATCH 0/2] signal/arc: siginfo cleanups
Date: Mon, 24 Sep 2018 16:47:44 +0200 [thread overview]
Message-ID: <874lef2bqn.fsf@xmission.com> (raw)
I have been slowly cleaning up the architectues ever since I discovered
that the pattern of passing in struct siginfo is error prone, and
occassionally results in borken siginfo being sent to userspace.
What is happening on arc is pretty tame and I have compile tested
these changes, so I don't expect problems.
Still I would appreciate if people can look over the code and perhaps
test it and see if they can spot anything that has perhaps gone wrong.
appreciate it.
My intention is to merge this through my siginfo tree. If you feel it
should go through your arch tree let me know. All of the prerequisites
should have been merged several releases ago.
Eric W. Biederman (2):
signal/arc: Push siginfo generation into unhandled_exception
signal/arc: Use force_sig_fault where appropriate
arch/arc/kernel/traps.c | 22 ++++++++--------------
arch/arc/mm/fault.c | 20 +++++---------------
2 files changed, 13 insertions(+), 29 deletions(-)
next reply other threads:[~2018-09-24 14:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:47 Eric W. Biederman [this message]
2018-09-24 14:47 ` [REVIEW][PATCH 0/2] signal/arc: siginfo cleanups Eric W. Biederman
2018-09-24 14:47 ` Eric W. Biederman
2018-09-24 14:49 ` [REVIEW][PATCH 1/2] signal/arc: Push siginfo generation into unhandled_exception Eric W. Biederman
2018-09-24 14:49 ` Eric W. Biederman
2018-09-24 14:49 ` Eric W. Biederman
2018-09-24 17:37 ` Vineet Gupta
2018-09-24 17:37 ` Vineet Gupta
2018-09-24 14:49 ` [REVIEW][PATCH 2/2] signal/arc: Use force_sig_fault where appropriate Eric W. Biederman
2018-09-24 14:49 ` Eric W. Biederman
2018-09-24 17:37 ` Vineet Gupta
2018-09-24 17:37 ` Vineet Gupta
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=874lef2bqn.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vgupta@synopsys.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 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.