public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Ben Widawsky <benjamin.widawsky@intel.com>
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Fix possible overflow when recording semaphore states.
Date: Fri, 18 Jul 2014 11:29:30 +0100	[thread overview]
Message-ID: <20140718102930.GA31263@strange.amr.corp.intel.com> (raw)
In-Reply-To: <20140717213114.GA3488@intel.com>

On Thu, Jul 17, 2014 at 02:31:14PM -0700, Ben Widawsky wrote:
> > -	for_each_ring(useless, dev_priv, i) {
> > +	for_each_ring(to, dev_priv, i) {
> >  		u16 signal_offset =
> >  			(GEN8_SIGNAL_OFFSET(ring, i) & PAGE_MASK) / 4;
> >  		u32 *tmp = error->semaphore_obj->pages[0];
> > +		int idx = intel_ring_sync_index(ring, to);
> >  
> > -		ering->semaphore_mboxes[i] = tmp[signal_offset];
> > -		ering->semaphore_seqno[i] = ring->semaphore.sync_seqno[i];
> > +		ering->semaphore_mboxes[idx] = tmp[signal_offset];
> > +		ering->semaphore_seqno[idx] = ring->semaphore.sync_seqno[idx];
> >  	}
> >  }
> >  
> This patch looks correct to me.

We're still looping over all the rings aren't we? we'll override the
array when ring == to?

-- 
Damien

  reply	other threads:[~2014-07-18 10:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 12:35 [PATCH] drm/i915: Fix possible overflow when recording semaphore states Rodrigo Vivi
2014-07-17 21:31 ` Ben Widawsky
2014-07-18 10:29   ` Damien Lespiau [this message]
2014-07-18  8:39     ` Rodrigo Vivi
2014-07-18 15:47       ` Damien Lespiau
2014-07-18  9:05         ` Rodrigo Vivi
2014-07-18 16:12           ` Damien Lespiau
2014-07-18  9:19             ` Rodrigo Vivi
2014-07-19  2:00               ` Ben Widawsky
2014-07-21  9:20                 ` Daniel Vetter

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=20140718102930.GA31263@strange.amr.corp.intel.com \
    --to=damien.lespiau@intel.com \
    --cc=benjamin.widawsky@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    /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