mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peng Fan <van.freenix@gmail.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Peng Fan <b51431@freescale.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] iommu: arm-smmu: correct reference count
Date: Mon, 9 Nov 2015 13:41:45 +0800	[thread overview]
Message-ID: <20151109054143.GA5704@linux-jyl1.ap.freescale.net> (raw)
In-Reply-To: <20151106122338.GI6087@arm.com>

Hi Will,

On Fri, Nov 06, 2015 at 12:23:39PM +0000, Will Deacon wrote:
>On Wed, Nov 04, 2015 at 10:48:28AM +0800, Peng Fan wrote:
>> On Tue, Nov 03, 2015 at 01:17:34PM +0000, Will Deacon wrote:
>> >On Tue, Nov 03, 2015 at 08:59:17PM +0800, Peng Fan wrote:
>> >> iommu_group_alloc will initialize the reference count for group to 1.
>> >> iommu_group_add_device also increase the group reference count,
>> >> if nothing bad happends. And we need to add iommu_group_put to
>> >> decrease the reference count for group.
>> >> 
>> >> Signed-off-by: Peng Fan <van.freenix@gmail.com>
>> >> Cc: Will Deacon <will.deacon@arm.com>
>> >> Cc: Joerg Roedel <joro@8bytes.org>
>> >> ---
>> >> 
>> >> Not sure whether my understanding is correct or not. I checked rockchip-iommu.c
>> >> exynos-iommu.c and fsl_pamu_domain.c, and they all have iommu_group_put after
>> >> iommu_group_add_device.
>> >
>> >Doesn't this pair up with the iommu_group_remove_device in
>> >arm_smmu_remove_device? Are you actually seeing an issue in practice?
>> 
>> In arm_smmu_add_platform_device,
>> iommu_group_alloc --> group->device_kobj ref count will be init to 1.
>> iommu_group_add_device --> group->device_kobj ref count will be added 1 to 2.
>> 
>> In arm_smmu_remove_device:
>> iommu_group_remove_device --> Decrease group->device_kobj ref count by 1.
>> After arm_smmu_remove_device, the ref count of group->device_kobj is not 0.
>> 
>> So I think need to add iommu_group_put after iommu_group_add_device.
>> If I am wrong, please correct me.
>
>Ok, I see what you're saying. iommu_group_get_for_dev has exactly the
>same issue, so could you update arm-smmu-v3.c as well, please?

I did not see the update about device_group for iommu, when I worked out this patch.
Rebased to latest linux/master, whether to arm-smmu.c or arm-smmu-v3.c,
only add 'iommu_group_put' at the end of iommu_group_get_for_dev is ok as the
following.

I'll send out V2.

Thanks,
Peng.

>
>Thanks,
>
>Will

      reply	other threads:[~2015-11-09  5:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 12:59 Peng Fan
2015-11-03 13:17 ` Will Deacon
2015-11-04  2:48   ` Peng Fan
2015-11-06 12:23     ` Will Deacon
2015-11-09  5:41       ` Peng Fan [this message]

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=20151109054143.GA5704@linux-jyl1.ap.freescale.net \
    --to=van.freenix@gmail.com \
    --cc=b51431@freescale.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will.deacon@arm.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

all inboxes | Powered by JetHome®