linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>,
	linux-alpha@vger.kernel.org, Richard Henderson <rth@twiddle.net>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Matt Turner <mattst88@gmail.com>
Subject: Re: alpha patches for v4.4.y / v4.9.y
Date: Mon, 15 Mar 2021 09:24:55 +0100	[thread overview]
Message-ID: <YE8Z1wFiRo2SOY33@kroah.com> (raw)
In-Reply-To: <44a392c3-418d-3503-7c46-0d283134d980@roeck-us.net>

On Sun, Mar 14, 2021 at 11:33:08AM -0700, Guenter Roeck wrote:
> Hi,
> 
> I recently started to add basic networking tests to my qemu test environment.
> When adding the necessary build options to Alpha kernels, I noticed that v4.4.y
> and v4.9.y no longer build due to relocation errors such as
> 
> net/built-in.o: In function `__copy_tofrom_user_nocheck':
> arch/alpha/include/asm/uaccess.h:364:(.text+0xff444):
> 		relocation truncated to fit: BRSGP against symbol `__copy_user'
> 
> The following patches fix the problem.
> 
> v4.9.y:
> 
> 5ed78e5523fd alpha: add $(src)/ rather than $(obj)/ to make source file path
> e19a4e3f1bff alpha: merge build rules of division routines
> 3eec0291830e alpha: make short build log available for division routines
> 4758ce82e667 alpha: Package string routines together
> 
> 8525023121de alpha: switch __copy_user() and __do_clean_user() to normal calling conventions
> 
> v4.4.y:
> 
> 5ed78e5523fd alpha: add $(src)/ rather than $(obj)/ to make source file path
> e19a4e3f1bff alpha: merge build rules of division routines
> 3eec0291830e alpha: make short build log available for division routines
> 4758ce82e667 alpha: Package string routines together
> 
> 00fc0e0dda62 alpha: move exports to actual definitions
> 085354f90796 alpha: get rid of tail-zeroing in __copy_user()
> 8525023121de alpha: switch __copy_user() and __do_clean_user() to normal calling conventions
> 
> Only the last patch of each group is really needed; I pulled the other
> patches in to avoid conflicts.
> 
> Please consider adding those patches to the respective kernels.

All now queued up, thanks.

greg k-h

      reply	other threads:[~2021-03-15  8:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-14 18:33 alpha patches for v4.4.y / v4.9.y Guenter Roeck
2021-03-15  8:24 ` Greg Kroah-Hartman [this message]

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=YE8Z1wFiRo2SOY33@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mattst88@gmail.com \
    --cc=rth@twiddle.net \
    --cc=stable@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).