mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.18.55
Date: Thu, 25 May 2017 20:50:43 +0200	[thread overview]
Message-ID: <20170525185043.GB17345@kroah.com> (raw)
In-Reply-To: <a4d32745-5c40-0f79-08fe-8044d0bcf56a@manjaro.org>

On Thu, May 25, 2017 at 08:32:19PM +0200, Philip Müller wrote:
> Hi there,
> 
> adding following patch[1] will result in following error on 32bit host:
> 
>   CC [M]  arch/x86/crypto/twofish_glue.o
>   AS [M]  arch/x86/crypto/salsa20-i586-asm_32.o
>   CC      fs/open.o
> kernel/fork.c: In function ‘dup_task_struct’:
> kernel/fork.c:341:22: error: implicit declaration of function
> ‘get_random_long’ [-Werror=implicit-function-declaration]
>   tsk->stack_canary = get_random_long();
>                       ^~~~~~~~~~~~~~~
>   CC      fs/read_write.o
> ...
>   LD      security/integrity/built-in.o
> cc1: some warnings being treated as errors
> make[1]: *** [scripts/Makefile.build:257: kernel/fork.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
>   CC      security/keys/gc.o
>   CC      ipc/ipcns_notifier.o
> 
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-3.18/stackprotector-increase-the-per-task-stack-canary-s-random-range-from-32-bits-to-64-bits-on-64-bit-platforms.patch

Didn't I drop this patch from the queue?  Oh crap, I only dropped it
from 4.4, sorry about that, I'll go revert it for the next release, my
fault.

greg k-h

  reply	other threads:[~2017-05-25 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 18:32 Philip Müller
2017-05-25 18:50 ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-05-25 16:18 Greg KH
2017-05-25 16:18 ` Greg KH

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=20170525185043.GB17345@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philm@manjaro.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

Powered by JetHome