From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201023] New: amdgpu fails compilation
Date: Wed, 05 Sep 2018 12:22:13 +0000 [thread overview]
Message-ID: <bug-201023-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=201023
Bug ID: 201023
Summary: amdgpu fails compilation
Product: Drivers
Version: 2.5
Kernel Version: 4.18
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: johnypean@gmail.com
Regression: No
Created attachment 278317
--> https://bugzilla.kernel.org/attachment.cgi?id=278317&action=edit
CONFIG_FORTIFY_SOURCE causes amdgpu to fail compilation
amdgpu driver (DC part) fails compilation when compiling with
CONFIG_FORTIFY_SOURCE option:
In function ‘memmove’,
inlined from ‘append_entry’ at
drivers/gpu/drm/amd/amdgpu/../display/dc/basics/logger.c:258:2,
inlined from ‘dm_logger_append_va.part.5’ at
drivers/gpu/drm/amd/amdgpu/../display/dc/basics/logger.c:349:4:
./include/linux/string.h:356:4: error: call to ‘__read_overflow2’ declared with
attribute error: detected read beyond size of object passed as 2nd parameter
__read_overflow2();
^~~~~~~~~~~~~~~~~~
I have attached a patch which resolves this problem.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-09-05 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 12:22 bugzilla-daemon [this message]
2018-09-05 14:03 ` [Bug 201023] amdgpu fails compilation bugzilla-daemon
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=bug-201023-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 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.