From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D05F835CB7C for ; Fri, 14 Aug 2026 14:10:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786716638; cv=none; b=dOQu14HrLs1SI4CWcjlBPkXU3zemHxcFN24R5WlqysdYynVQSgJKVC3ZAD/gmqJvwG23qPR7tT27qjbenlB643EpGc9ADP4Jbq8FC5uPsYSD9rjA7H9/rn8/5ht3DG06VkgpWrxHR3Sb0rfEy5rSQHWDF5menzp2UibhL//SPeY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786716638; c=relaxed/simple; bh=+iP5+EoaT6MglIrU5cLxcaTlWSHccKQqB3RjQlhXHqg=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=GYxcRqg01DKtApmNyYaRKnx+at3CPUWtZv+O0WyU13wjqrSAt0dDJFDeRS4iGIGXaDFFRwpmw8bqd2pyU6ZYX6LPpT3fxMp72nR7psXFjvvCUXQ1VzxOkQkLxjLL1bfpbjEtBPT9oM9A5Q3CcYqQWWxgCe/u6RMXc091tBnecIw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ZhG/Qnns; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ZhG/Qnns" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CEA7F1F000E9; Fri, 14 Aug 2026 14:10:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1786716637; bh=Wbh+GzwLRDj8K6sa4FaLievOQOmn4W4a+vnrgcHiZ+8=; h=From:To:Cc:Subject:In-Reply-To:References:Date; b=ZhG/QnnswWAQ8Kb14R80WrGND45IGsu7pq9K3Zs6upUv1ewBLaIalY9bF9lHRwqs1 o3il654JMBsdt82inwc+47Wf1d2YGzsDSlqpOSn3EkbRtBuTaJQT63DVPzJpocAAVy JeNpgzRDLx4N+jiN3aczRZ1KeLlcQSqVXlVQeR35syUYLRhCuFrEbYQ47JjNjzrmKR snmY0MCaUo4Hj5AGg0dGEAlAftnDOW5rddY13lMgxP0DPXjgMdnUCpzldC6fY8H6L9 rKTDqdOoXu9FDVnpkwsdFcJoF1/uZiJXImnygWHkiX0xChVIY+/8NACnIT9B2U3DPJ SLyf4jkJ6GmoA== From: Pratyush Yadav To: Chenghao Duan Cc: pasha.tatashin@soleen.com, rppt@kernel.org, pratyush@kernel.org, graf@amazon.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, kexec@lists.infradead.org, jianghaoran@kylinos.cn Subject: Re: [PATCH] liveupdate: use scoped_guard for mutex in session operations In-Reply-To: <20260814095506.631274-1-duanchenghao@kylinos.cn> (Chenghao Duan's message of "Fri, 14 Aug 2026 17:55:06 +0800") References: <20260814095506.631274-1-duanchenghao@kylinos.cn> Date: Fri, 14 Aug 2026 16:10:34 +0200 Message-ID: <2vxzzeyo23ol.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Fri, Aug 14 2026, Chenghao Duan wrote: > Replace manually paired mutex_lock/unlock with scoped_guard to align > with the coding style of the rest of the codebase and simplify locking > paths. No. This is done explicitly because we don't want to mix gotos with the automatic cleanup-style locking. I don't think we should change this. [...] -- Regards, Pratyush Yadav