summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorThierry Reding <treding@nvidia.com>2019-09-16 17:19:23 +0300
committerBen Skeggs <bskeggs@redhat.com>2019-09-17 07:50:15 +0300
commit9ca7f7968be74ebf02f3a89d605d36bcb636560e (patch)
treee00316844cb29b935146964e4e14e8c9ca3412b8 /scripts/gdb/linux/utils.py
parent698c1aa9f83b618de79e9e5e19a58f70a4a6ae0f (diff)
downloadlinux-9ca7f7968be74ebf02f3a89d605d36bcb636560e.tar.xz
drm/nouveau: Fix fallout from reservation object rework
Commit 019cbd4a4feb ("drm/nouveau: Initialize GEM object before TTM object") introduced a subtle change in how the buffer allocation size is handled. Prior to that change, the size would get aligned to at least a page, whereas after that change a non-page-aligned size would get passed through unmodified. This ultimately causes a BUG_ON() to trigger in drm_gem_private_object_init() and crashes the system. Fix this by restoring the code that align the allocation size. Fixes: 019cbd4a4feb ("drm/nouveau: Initialize GEM object before TTM object") Reported-by: Ilia Mirkin <imirkin@alum.mit.edu> Signed-off-by: Thierry Reding <treding@nvidia.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions