Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Michael Ellerman <patch-notifications@ellerman.id.au>
To:     mpe@ellerman.id.au, Qian Cai <cai@lca.pw>
Cc:     linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
        paulus@samba.org, aik@ozlabs.ru, paulmck@kernel.org
In-Reply-To: <20200510051559.1959-1-cai@lca.pw>
References: <20200510051559.1959-1-cai@lca.pw>
Subject: Re: [PATCH] powerpc/mm/book3s64/iommu: fix some RCU-list locks
Message-Id: <161235200882.1516112.5579154052220245435.b4-ty@ellerman.id.au>
Date:   Wed,  3 Feb 2021 22:40:02 +1100 (AEDT)
Precedence: bulk

On Sun, 10 May 2020 01:15:59 -0400, Qian Cai wrote:
> It is safe to traverse mm->context.iommu_group_mem_list with either
> mem_list_mutex or the RCU read lock held. Silence a few RCU-list false
> positive warnings and fix a few missing RCU read locks.
> 
>  arch/powerpc/mm/book3s64/iommu_api.c:330 RCU-list traversed in non-reader section!!
> 
>  other info that might help us debug this:
> 
> [...]

Applied to powerpc/next.

[1/1] powerpc/mm/book3s64/iommu: fix some RCU-list locks
      https://git.kernel.org/powerpc/c/b5952f8125ae512420d5fc569adce591bea73bf5

cheers