From: Dan Carpenter <dan.carpenter@oracle.com>
To: chris@chris-wilson.co.uk
Cc: intel-gfx@lists.freedesktop.org
Subject: [bug report] drm/i915: Allow compaction upto SWIOTLB max segment size
Date: Mon, 14 Nov 2016 14:14:56 +0300 [thread overview]
Message-ID: <20161114111455.GA13441@mwanda> (raw)
Hello Chris Wilson,
The patch 871dfbd67d4e: "drm/i915: Allow compaction upto SWIOTLB max
segment size" from Oct 11, 2016, leads to the following static
checker warning:
drivers/gpu/drm/i915/i915_gem.c:2357 i915_gem_object_get_pages_gtt()
error: we previously assumed 'sg' could be null (see line 2341)
drivers/gpu/drm/i915/i915_gem.c
2339 /* Check that the i965g/gm workaround works. */
2340 WARN_ON((gfp & __GFP_DMA32) && (last_pfn >= 0x00100000UL));
2341 }
2342 if (sg) /* loop terminated early; short sg table */
We added a new check for NULL.
2343 sg_mark_end(sg);
2344
2345 /* Trim unused sg entries to avoid wasting memory. */
2346 i915_sg_trim(st);
2347
2348 ret = i915_gem_gtt_prepare_pages(obj, st);
2349 if (ret)
2350 goto err_pages;
but we hit this goto
2351
2352 if (i915_gem_object_needs_bit17_swizzle(obj))
2353 i915_gem_object_do_bit_17_swizzle(obj, st);
2354
2355 return st;
2356
2357 err_pages:
2358 sg_mark_end(sg);
Then don't check here. Also do we really need to sg_mark_end() twice?
2359 for_each_sgt_page(page, sgt_iter, st)
2360 put_page(page);
2361 sg_free_table(st);
2362 kfree(st);
regards,
dan carpenter
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-11-14 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 11:14 Dan Carpenter [this message]
2016-11-14 11:23 ` [bug report] drm/i915: Allow compaction upto SWIOTLB max segment size Chris Wilson
2016-11-14 11:29 ` [PATCH] drm/i915: Don't touch NULL sg on i915_gem_object_get_pages_gtt() error Chris Wilson
2016-11-18 17:19 ` Matthew Auld
2016-11-18 20:52 ` [Intel-gfx] " Chris Wilson
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=20161114111455.GA13441@mwanda \
--to=dan.carpenter@oracle.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).