From: Emmanuel Florac <eflorac@intellique.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel 3.18.55 compilation fails (missing function declaration)
Date: Fri, 2 Jun 2017 15:30:47 +0200 [thread overview]
Message-ID: <20170602153047.2978ee6c@harpe.intellique.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
Hi, kernel 3.18.55 compilation fails with this error:
kernel/fork.c: In function ‘dup_task_struct’:
kernel/fork.c:341:2: error: implicit declaration of function
‘get_random_long’ [-Werror=implicit-function-declaration]
tsk->stack_canary = get_random_long();
Corrected by adding the declaration to include/linux/random.h line 26 :
unsigned long get_random_long(void);
Sorry, I really can't understand how to generate a patch from a tagged
release, my git-fu is far too low...
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2017-06-02 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 13:30 Emmanuel Florac [this message]
2017-06-08 22:10 ` Randy Dunlap
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=20170602153047.2978ee6c@harpe.intellique.com \
--to=eflorac@intellique.com \
--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
all inboxes | Powered by JetHome®