From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta0.migadu.com (out-38.mta0.migadu.com [91.218.175.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2AE3042AA9 for ; Sat, 15 Aug 2026 04:16:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.38 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786767364; cv=none; b=QO+EtPkKJVDVXJzZwWVMEAlDoVDms9fF6CZKw8J2cnwRC/EbF7yUjwF9nLiyJNrvzsXX5jar8jHabFI1MoEQ+x9ZIqIyJnE5O1x6RHxfCIPJGFnxvbWy4BLDmjLT+TuEljtWfDXQNHiFMQGWIuz40h1aeeq6UvXrXLfghxvIU0k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786767364; c=relaxed/simple; bh=y3K7b6ckx2Hltas4lYepUcEXu3vNRV1wOWoPphH5tTA=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=KnFXV8RPMIii7NxG8AgZZgmefeUZycnDqEnHfT7XK0uqBWiTendH0g/TMhz5yxErAERZvK6yD6nUx4gtI8fPYZmjbXWeZUEik1Pp0/QcYZX60PnMOc+wfPbZM8NJ3Y8yctPOw9mByrIXVWcHihSNg9vLrOavRfQAJRTAdN6da7M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=G5mZEqQ6; arc=none smtp.client-ip=91.218.175.38 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="G5mZEqQ6" X-Envelope-To: linux-kernel@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=y3K7b6ckx2Hltas4lYepUcEXu3vNRV1wOWoPphH5tTA=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1786767359; v=1; x=1787372159; b=G5mZEqQ6LnD8bSDJbWEXDKeLE5ZYVSDmjjWsYAUu/ygOFUgoitVo2j7uhwWyKlbDoV60AOq7 aqnvdU7Tcx0Lc8GIT7jruvfhlwTof2bhhVgksqTZnf0m8EHNaoXxqlO8o62FoM2VKsgiSUwNhOk Rb2+U00Ju6i8A6p0Wk/0HeX4= X-Envelope-To: linux-kernel@vger.kernel.org Received: from localhost (183.241.20.126) by smtp.migadu.com with ESMTPS id b647dc149dd61193; Sat, 15 Aug 2026 04:15:59 +0000 X-Migadu-Flow: FLOW_OUT From: Lance Yang To: seohyun.kim@outlook.kr Cc: akpm@linux-foundation.org, david@kernel.org, ljs@kernel.org, riel@surriel.com, liam@infradead.org, vbabka@kernel.org, harry@kernel.org, jannh@google.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Lance Yang Subject: Re: [PATCH] mm/rmap: synchronize lock and unlock target in anon_vma_clone Date: Sat, 15 Aug 2026 12:15:51 +0800 Message-Id: <20260815041551.84041-1-lance.yang@linux.dev> X-Mailer: git-send-email 2.39.3 (Apple Git-146) In-Reply-To: References: Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On Fri, Aug 14, 2026 at 03:30:51PM +0900, Eric Kim wrote: >Currently, in anon_vma_clone(), src vma's anon_vma is assigned to >active_anon_vma and is used when unlocking anon_vma after linking new >AVCs. However, the anon_vma is locked using src->anon_vma, instead of >active_anon_vma, making the lock and unlock target inconsistent. > >Use active_anon_vma for both locking and unlocking. > >Signed-off-by: Eric Kim >--- Reviewed-by: Lance Yang