All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victor Kamensky <kamensky@cisco.com>
To: linux-mips@vger.kernel.org, Paul Burton <paulburton@kernel.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <jhogan@kernel.org>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	bruce.ashfield@gmail.com, richard.purdie@linuxfoundation.org
Subject: [PATCH v2 0/2] mips: vdso: fix 'jalr t9' crash in vdso code
Date: Tue, 11 Feb 2020 11:24:32 -0800	[thread overview]
Message-ID: <20200211192434.24871-1-kamensky@cisco.com> (raw)

Hi Paul and all,

Here is the second version of patch set dealing with 'jalr t9'
crash in vdso code. Root cause and investigation details could be
found in first version cover letter for this patch series [1].

Changes in v2:
   - added -mrelax-pic-calls -mexplicit-relocs unconditionally
     (dropped 'call cc-option') since minimal supported gcc version
     already has them
   - fixed few misspellings in commit messages
   - added explanation in commit messages about handling static
     functions PIC calls through mips local GOT and absence of dynamic
     relocations in this case

Thanks,
Victor

[1] https://lore.kernel.org/linux-mips/20200203233133.38613-1-kamensky@cisco.com

Victor Kamensky (2):
  mips: vdso: fix 'jalr t9' crash in vdso code
  mips: vdso: add build time check that no 'jalr t9' calls left

 arch/mips/vdso/Makefile | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

-- 
2.24.1


             reply	other threads:[~2020-02-11 19:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 19:24 Victor Kamensky [this message]
2020-02-11 19:24 ` [PATCH v2 1/2] mips: vdso: fix 'jalr t9' crash in vdso code Victor Kamensky
2020-02-11 19:24 ` [PATCH v2 2/2] mips: vdso: add build time check that no 'jalr t9' calls left Victor Kamensky
2020-02-15 22:55 ` [PATCH v2 0/2] mips: vdso: fix 'jalr t9' crash in vdso code Paul Burton

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=20200211192434.24871-1-kamensky@cisco.com \
    --to=kamensky@cisco.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=jhogan@kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=vincenzo.frascino@arm.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.