From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-m17238.xmail.ntesmail.com (mail-m17238.xmail.ntesmail.com [45.195.17.238]) (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 33EEF17992 for ; Fri, 22 Dec 2023 11:08:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=easystack.cn Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=easystack.cn Received: from [10.9.0.94] (unknown [211.103.144.18]) by smtp.qiye.163.com (Hmail) with ESMTPA id BEF3A4C0174; Fri, 22 Dec 2023 19:08:09 +0800 (CST) Message-ID: <5a791f12-9c88-4dca-ac9d-dee4ba36bf9c@easystack.cn> Date: Fri, 22 Dec 2023 19:08:09 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 2/2] kexec: Fix potential out of bounds in crash_exclude_mem_range() To: Baoquan He Cc: Vivek Goyal , Dave Young , Yuntao Wang , kexec@lists.infradead.org, linux-kernel@vger.kernel.org References: <20231220055733.100325-1-fuqiang.wang@easystack.cn> <20231220055733.100325-3-fuqiang.wang@easystack.cn> Content-Language: en-US From: fuqiang wang In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFJQjdXWS1ZQUlXWQ8JGhUIEh9ZQVkZHUhNVk1CSElOHUMfSk1LQ1UZERMWGhIXJBQOD1 lXWRgSC1lBWUlKSlVKS0hVSk9PVUpDWVdZFhoPEhUdFFlBWU9LSFVKTU9JTE5VSktLVUpCS0tZBg ++ X-HM-Tid: 0a8c9136165c022ekunmbef3a4c0174 X-HM-MType: 1 X-HM-Sender-Digest: e1kMHhlZQR0aFwgeV1kSHx4VD1lBWUc6Mk06Qgw5Hjc#ISgKAhE9NR4B MBcKCUNVSlVKTEtISU9ISUJLTk9DVTMWGhIXVR0OChIaFRxVDBoVHDseGggCCA8aGBBVGBVFWVdZ EgtZQVlJSkpVSktIVUpPT1VKQ1lXWQgBWUFKQ0NMNwY+ 在 2023/12/21 19:42, Baoquan He 写道: > You may need rebase your work on next/master branch to avoid conflict. > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > In the current, below commit exists, then code change in this patch may > not be needed. > 86d80cbb61ca crash_core: fix and simplify the logic of crash_exclude_mem_range() > Yes, Baoquan, you are right. It's my mistake. Thank you very much ~