From mboxrd@z Thu Jan 1 00:00:00 1970 From: Doug Ledford Subject: Re: [PATCH rdma-next 1/4] IB/mlx4: Take write semaphore when changing the vma struct Date: Mon, 24 Apr 2017 12:12:48 -0400 Message-ID: <1493050368.3041.37.camel@redhat.com> References: <20170329030303.4942-1-leon@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <20170329030303.4942-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Leon Romanovsky Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Maor Gottlieb List-Id: linux-rdma@vger.kernel.org On Wed, 2017-03-29 at 06:03 +0300, Leon Romanovsky wrote: > From: Maor Gottlieb > > When the driver disassociate user context, it changes the vma to > anonymous by setting the vm_ops to null and zap the vma ptes. > > In order to avoid race in the kernel, we need to take write lock > before we change the vma entries. > > Fixes: ae184ddeca5db ('IB/mlx4_ib: Disassociate support') > Signed-off-by: Maor Gottlieb > Signed-off-by: Leon Romanovsky Thanks, series applied. -- Doug Ledford     GPG KeyID: B826A3330E572FDD     Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html