From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.10]) (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 3C5C32C08BB; Thu, 11 Jun 2026 19:33:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.10 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781206422; cv=none; b=aBMKpr9ZR3TgJ5ySp8L5h82+D/XbWg8JKd5Oal6fwv+SD9kXbk2EtssBXqsILPrNI2XbmwLCOMu02wwV1YhIutfLTKZmHJYs97sx5kAMKX09mPA6/wq8K7HNpB1k+eMt1CpsobjBryZDL9A8MSxVqzGZuOsA8zfTgsIm0yu7Bbs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781206422; c=relaxed/simple; bh=NIR3HYw2JEH9d+Wwq9mB8fwmfiQAFUYzbs2IS3Faf5A=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=rlbJ07OxW4Z3DR1Ok95ydQfYHULF6hEOIP3e/uoXcOsAQDXrVgMHikAchH7aHfWSIBactSGUsBGFKEwPAdr+7gBrmg+Y6fYHRTB0Ma0XbmtMAI3NTlmQQa2UMRefDZozddnFOIApEDEk3WWFkvTyR/e3XYNyt9ilaHm7SaCt9XA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=FfFjcYBx; arc=none smtp.client-ip=192.198.163.10 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="FfFjcYBx" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1781206421; x=1812742421; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=NIR3HYw2JEH9d+Wwq9mB8fwmfiQAFUYzbs2IS3Faf5A=; b=FfFjcYBx9MQIIR1Frhud//03y/aeGDQMfvoQEGTyYULwQDP4NRJSf2aG kTnEQ6GMrGdmpFOARPlA8ntgNXHXd3tidUkfkxwbdUAVRgDpbN+hTKJHx XUeYwABl+EJN9IwKpUaVbPSfMSbvDMDKGYMj+kOboItesPd5PV6gVvwvZ H+dd+Ap5b0oQxL8embAMAWVNC8wJW1SovWAngYRaZduWaMXNjqV2XarbA stIu2xhIjmfnVRTym6g2oRXj9D5cdzxDLf/ptaqdO1FUUoxUxQa9BQaS+ 4UHp0ONaCNEcZwjDVMhuGek9xsDmzlS50wSbvZEpvsn/yO/oahrLJvhmk Q==; X-CSE-ConnectionGUID: DEVnIBUKT2S39H9gWKjS/Q== X-CSE-MsgGUID: e3Ocs9cdT1yLYovnd9CFnQ== X-IronPort-AV: E=McAfee;i="6800,10657,11813"; a="93423640" X-IronPort-AV: E=Sophos;i="6.24,199,1774335600"; d="scan'208";a="93423640" Received: from fmviesa001.fm.intel.com ([10.60.135.141]) by fmvoesa104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jun 2026 12:33:40 -0700 X-CSE-ConnectionGUID: 0wSjZKvyRlKvpIUqpBVZeg== X-CSE-MsgGUID: 1y256R2mT72GQJAJDpkyFA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.24,199,1774335600"; d="scan'208";a="270614781" Received: from ettammin-mobl3.ger.corp.intel.com (HELO localhost) ([10.245.244.123]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 11 Jun 2026 12:33:37 -0700 Date: Thu, 11 Jun 2026 22:33:35 +0300 From: Andy Shevchenko To: Matthew Wilcox Cc: Anshuman Khandual , linux-mm@kvack.org, Rasmus Villemoes , Sergey Senozhatsky , Petr Mladek , Steven Rostedt , Jonathan Corbet , Andrew Morton , David Hildenbrand , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [RFC V2 0/3] lib/vsprintf: Add support for pgtable entries Message-ID: References: <20260610043545.3725735-1-anshuman.khandual@arm.com> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Thu, Jun 11, 2026 at 08:15:57PM +0100, Matthew Wilcox wrote: > On Wed, Jun 10, 2026 at 05:35:42AM +0100, Anshuman Khandual wrote: > > Printing page table entries has been a common requirement both in generic > > and platform memory management for various purposes. Hence let's create a > > dedicated printk format for such entries which will also help standardize > > pgtable printing across different platforms. > > You didn't address my objection here: > > https://lore.kernel.org/linux-mm/aFQP8LzVMctf6XH5@casper.infradead.org/ > > ie there is now no typechecking possible. So you've made it more > dangerous. I reiterate my NACK to the concept, not to the implementation. But this is more of a global question, how do we check the validity of the parameters of pointer extensions in the kernel? Does anybody go to commit into GCC plugin or so for this job? -- With Best Regards, Andy Shevchenko