From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-183.mta0.migadu.com (out-183.mta0.migadu.com [91.218.175.183]) (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 B89B522F77B for ; Tue, 7 Apr 2026 02:07:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.183 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775527649; cv=none; b=S/Td3rvduIRB3yac7hCehzE4faBMTvlXWW4TcE9OseO7M7Z70QVnVPSgDAl5OmeMp9EpEMupzEdJk1zEoJZdqD/A4qgMilrbQuOPNFFtDzVlqu6s1ny1578qsGAehl/YWiA5NtAAl3XrqiSgEOyTHdpU2cNcaJQgL5GMgSIPDMw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775527649; c=relaxed/simple; bh=9ufPDArJHo4vh9986lIOLLrY4nC2Li80mY9Vpodh2Ns=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=lElNvmI1v/pRqv4Z5wJ2ySn/FNhD4DAYwlFzmNZU8N9x+eIfNJ70fQRxakdXcV48VojkwlvLskFQWDS6w0BskcRQGuoKsWynKWNCj8YAcxwHyL4Fv2bp7Q+bYu+EhxBwh7J8XUp9sYvmjvpU8HvIuhWLO4CDfZOZkQ03NhYcRyE= 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=YO0NMKTm; arc=none smtp.client-ip=91.218.175.183 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="YO0NMKTm" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1775527645; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FjMxtyhJaFG5pOQOqH2K0+MdO1zIjVmI2OgbGlmSS28=; b=YO0NMKTmD2znsF9cjxHJYmmXM/sq6DtV7ZMmrvc+6adr5Txo+e9agPGjghfMa+XHDhPhpx eHqgmU58BE6Spk+lb2EXYbzn5C/avOe9Dirsp4SdKnf9160aBF5EpnL170MrKRJfSuDY+d LT2TghsFGGF1jpRte+lH2OXp3GE87ps= From: Ye Liu To: Miaohe Lin , Andrew Morton Cc: Ye Liu , Naoya Horiguchi , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: [PATCH 2/2] mm/memory-failure: use bool for forcekill state Date: Tue, 7 Apr 2026 10:07:13 +0800 Message-ID: <20260407020715.2269255-3-ye.liu@linux.dev> In-Reply-To: <20260407020715.2269255-1-ye.liu@linux.dev> References: <20260407020715.2269255-1-ye.liu@linux.dev> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT From: Ye Liu 'forcekill' is used as a boolean flag to control whether processes should be forcibly killed. It is only assigned from boolean expressions and never used in arithmetic or bitmask operations. Convert it from int to bool. No functional change intended. Signed-off-by: Ye Liu --- mm/memory-failure.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mm/memory-failure.c b/mm/memory-failure.c index d25adb390c3e..f355642bc2b6 100644 --- a/mm/memory-failure.c +++ b/mm/memory-failure.c @@ -459,7 +459,7 @@ void add_to_kill_ksm(struct task_struct *tsk, const struct page *p, * Only do anything when FORCEKILL is set, otherwise just free the * list (this is used for clean pages which do not need killing) */ -static void kill_procs(struct list_head *to_kill, int forcekill, +static void kill_procs(struct list_head *to_kill, bool forcekill, unsigned long pfn, int flags) { struct to_kill *tk, *next; @@ -1582,7 +1582,7 @@ static bool hwpoison_user_mappings(struct folio *folio, struct page *p, { LIST_HEAD(tokill); bool unmap_success; - int forcekill; + bool forcekill; bool mlocked = folio_test_mlocked(folio); /* -- 2.43.0