From: "Luck, Tony" <tony.luck@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
linux-ia64@vger.kernel.org, Fenghua Yu <fenghua.yu@intel.com>
Subject: Re: [REVIEW][PATCH 0/3] signal/ia64: siginfo fixes and cleanups
Date: Mon, 24 Sep 2018 10:38:20 -0700 [thread overview]
Message-ID: <20180924173818.GA9522@agluck-desk> (raw)
In-Reply-To: <87bm8n2czz.fsf@xmission.com>
On Mon, Sep 24, 2018 at 04:20:32PM +0200, Eric W. Biederman wrote:
>
> It turns out that ia64 is one of the noticable offenders. Ever since
> ia64 was merged in 2.3.43 it has been generating incorrect siginfo for
> SIGSEGV assocaited with the inability to setup a signal stack frame
> or cleanup a signal stack frame.
I'll blame that on the "previous administration". I didn't start work
on Linux until 2.3.99, and didn't take over as maintainer until 2.6.11 :-)
> I don't think I have made made any mistakes in this coversion but if
> people can look the code over and see if they can spot anything I would
> appreciate it.
I don't see any mistakes either. It builds and boots. Obviously I don't
have a test case for this issue (or it would have been found long ago).
> 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.
Sure. Merge away.
Acked-by: Tony Luck <tony.luck@intel.com>
-Tony
next prev parent reply other threads:[~2018-09-24 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 14:20 [REVIEW][PATCH 0/3] signal/ia64: siginfo fixes and cleanups Eric W. Biederman
2018-09-24 14:20 ` Eric W. Biederman
2018-09-24 17:38 ` Luck, Tony [this message]
2018-09-24 17:38 ` Luck, Tony
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=20180924173818.GA9522@agluck-desk \
--to=tony.luck@intel.com \
--cc=ebiederm@xmission.com \
--cc=fenghua.yu@intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).