From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 39320221FB4 for ; Thu, 30 Jul 2026 11:13:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785410001; cv=none; b=uhSXzDHL8nNtUzVGYPqr58dDJy2ugT/SynrKrLrvGNeqjZdWviY2XB4GC2t9/nl31iirvatInjhlio5VtyE7hIctff53CFlJG0/2tQ1EQkBoSGs/eF8DB0uGyB+LiD9w9vTDjDJUJmrXAGuZmMIZ4QxGPQWchztBae1UKRJcyHw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785410001; c=relaxed/simple; bh=lH50JkgMkIQTnJi2sXznS2de+Mdy9M0nQ4D9Pq1jSWs=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=RL+oB04g/9fdCeTwAWYiaLzTck743BPq5T1/IIVDDXYZl60Ak1KJIwUOyt5tu65A+8oCPodEoaTfJPOf8fzno5HGl9TKth7sJfEe2ZtoDLLfvXU2g0p2HXKOjDffzEx9s1LxjZzeWizFwIl4f1AghRK0YavRf9hhlpzjJTf4MKY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b=sr7OsiTr; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b="sr7OsiTr" Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id A02EA1684; Thu, 30 Jul 2026 04:13:15 -0700 (PDT) Received: from e142334-100.cambridge.arm.com (e142334-100.cambridge.arm.com [10.2.198.93]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id F06F63F763; Thu, 30 Jul 2026 04:13:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1785409999; bh=lH50JkgMkIQTnJi2sXznS2de+Mdy9M0nQ4D9Pq1jSWs=; h=From:To:Cc:Subject:Date:From; b=sr7OsiTr5W7aLt/z6YUdVQuMAA0aGXHqbGpV3wjtY0UYw3Hoe/3VGjLHCRhLoe9U8 aOe7Kn1C8N6wSSgll9rapoSiwc6+BcBKD+IJGBu2A0G/hr1TNG0SjBCuF9tsWZPVHD 57Tq585eUelkZsfqzEBqFTEs94xY7olgA1G3srZc= From: Muhammad Usama Anjum To: Dimitri Sivanich , Arnd Bergmann , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Cc: Muhammad Usama Anjum Subject: [PATCH 0/3] misc: sgi-gru: Remove broken page-table walks Date: Thu, 30 Jul 2026 12:12:49 +0100 Message-ID: <20260730111316.3672672-1-usama.anjum@arm.com> X-Mailer: git-send-email 2.47.3 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit While working on MM page-table changes, I found that the SGI GRU driver walks user page tables unsafely from interrupt context. This series removes that path, uses the existing process-context fallback, and cleans up the resulting dead code. Muhammad Usama Anjum (3): misc: sgi-gru: remove interrupt-context page-table walks misc: sgi-gru: remove obsolete atomic fault-handling state misc: sgi-gru: inline the user CBR status update drivers/misc/sgi-gru/grufault.c | 185 +++++++------------------------ drivers/misc/sgi-gru/gruprocfs.c | 1 - drivers/misc/sgi-gru/grutables.h | 1 - 3 files changed, 41 insertions(+), 146 deletions(-) -- 2.47.3