From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v3 10/13] xen/iommu: smmu: Check for duplicate stream IDs when registering master devices Date: Fri, 20 Feb 2015 12:35:23 +0000 Message-ID: <1424435723.30924.212.camel@citrix.com> References: <1422643768-23614-1-git-send-email-julien.grall@linaro.org> <1422643768-23614-11-git-send-email-julien.grall@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YOmo9-000438-Po for xen-devel@lists.xenproject.org; Fri, 20 Feb 2015 12:35:49 +0000 In-Reply-To: <1422643768-23614-11-git-send-email-julien.grall@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall Cc: Andreas Herrmann , xen-devel@lists.xenproject.org, Andreas Herrmann , tim@xen.org, stefano.stabellini@citrix.com List-Id: xen-devel@lists.xenproject.org On Fri, 2015-01-30 at 18:49 +0000, Julien Grall wrote: > From: Andreas Herrmann > > If DT information lists one stream ID twice for the master devices of > an SMMU this can cause a multi match when stream ID matching is used. > For stream ID indexing this might trigger an overwrite of an S2CR that > is already in use. > > So better check for duplicates when DT information is parsed. > > Taken from the linux ML: > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-January/226099.html > > Cc: Andreas Herrmann > Signed-off-by: Andreas Herrmann > Signed-off-by: Julien Grall I think you were going to drop this one as it is not strictly required? I'm still not entirely clear on the motivation for this patch, looking at the v2 thread I see "But, the developer made have written by mistake twice the streamid for the device." which I think you were saying that the DT might, hypothetically, be wrong and have duplicated IDs, is that right? Is it a hypothetical problem or have we seen it in a real device-tree? Ian.