From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194579] AMDGPU: Possible size overflow detected by PaX in ttm_bo_handle_move_mem (drivers/gpu/drm/ttm/ttm_bo.c:388)
Date: Thu, 16 Feb 2017 23:18:28 +0000 [thread overview]
Message-ID: <bug-194579-2300-dH4QvnyP3I@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194579-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194579
Nicolai Hähnle (nhaehnle@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nhaehnle@gmail.com
--- Comment #7 from Nicolai Hähnle (nhaehnle@gmail.com) ---
VRAM buffers can get split into multiple underlying memory chunks; in this
case, bo->mem.start == AMDGPU_BO_INVALID_OFFSET; it's not a logic bug.
bo->offset is only used via amdgpu_bo_gpu_offset, which has a WARN_ON_ONCE to
guard against accidental use of the field in this particular case.
Therefore, I'm inclined to say that this is probably not an actual bug.
--
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 prev parent reply other threads:[~2017-02-16 23:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 17:06 [Bug 194579] New: AMDGPU: Possible size overflow detected by PaX in ttm_bo_handle_move_mem (drivers/gpu/drm/ttm/ttm_bo.c:388) bugzilla-daemon
2017-02-13 17:10 ` [Bug 194579] " bugzilla-daemon
2017-02-14 7:42 ` bugzilla-daemon
2017-02-14 9:52 ` bugzilla-daemon
2017-02-14 9:55 ` bugzilla-daemon
2017-02-14 15:07 ` bugzilla-daemon
2017-02-14 22:19 ` bugzilla-daemon
2017-02-16 23:18 ` bugzilla-daemon [this message]
2017-02-17 10:05 ` bugzilla-daemon
2017-02-18 0:21 ` bugzilla-daemon
2017-02-21 9:24 ` bugzilla-daemon
2017-02-21 9:52 ` bugzilla-daemon
2017-02-21 13:19 ` 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-194579-2300-dH4QvnyP3I@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.