From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.16]) (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 548A01F5821 for ; Wed, 10 Jun 2026 14:59:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781103581; cv=none; b=cb5sVM67F+HCWagDOEV5aeInUkkKomYn6w9XK8ADilyWVqcB7yRJ+m4rnfevT3nOxNdNZUOxBNqASWAgM6drDmTuJ5Adxwwxmxqw+We6OKq6/rVBS4PNWySnGm1sXyCSJCKM+JXRrLZqB0083FSVTCjnLjR26YadgpPqWkKhe60= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781103581; c=relaxed/simple; bh=fYTs0e5mYVuWUXeROEDecmiYNj2zA2bnwOZxx+TRgrk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=NFg//+PnFVpVex1CfrWtAAaW2BclBJMDZoFNeI4Cs+VzNQUj2Asd8RXlG4Q2RiJxbB1nurcL4LdQCt3rGYGnPIKRtRJKud3xP533bbP+krROWwDbXae5uTt+1HYqB38MmtHboiYSz/4jCv+lvbviS6PBAKj7/HqDgLc7jGBpu+A= 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=hg5XcaEU; arc=none smtp.client-ip=192.198.163.16 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="hg5XcaEU" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1781103580; x=1812639580; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=fYTs0e5mYVuWUXeROEDecmiYNj2zA2bnwOZxx+TRgrk=; b=hg5XcaEU09fHhdSIBxRCHpUdEEESTUWEpsFbt2ujSNAf7eSTOn4huQrt ux7cm+qhiijyIvQNTsZrspyAKT/tHD889EQwL7fmW6a5jBZDvRej64fqe p1+9jhHPDCXL+aV63ad5ugR0FsXiGS/Ru7SdmB+ku6prpWJCWVieULYt+ Vdas7VElVWaX4YtZF6ZwmYbroct2MyhXEbPbSL6A+zrJx5PvqJs3yc9ET aytAGZT6JgK2W9jU68iwYevKaekDuKCnYteN7yO4XACr+HkTrtExgGNhw eeQbccwOKDFnai/WP1rGvgQpAPsTVXrnut4rNARZOlynfEgZGBbh/+M8O g==; X-CSE-ConnectionGUID: HAjF2fvFTpS0Rdt1DRy8IA== X-CSE-MsgGUID: nPd4RPQMTRWHBGK7pGgCqA== X-IronPort-AV: E=McAfee;i="6800,10657,11813"; a="69438996" X-IronPort-AV: E=Sophos;i="6.24,197,1774335600"; d="scan'208";a="69438996" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by fmvoesa110.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Jun 2026 07:59:38 -0700 X-CSE-ConnectionGUID: VMReEh/lQCanNBiEqivdDg== X-CSE-MsgGUID: /BNuCFpNSV+a6rUi9ozKyA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.24,197,1774335600"; d="scan'208";a="284280485" Received: from hrotuna-mobl2.ger.corp.intel.com (HELO localhost) ([10.245.244.38]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Jun 2026 07:59:35 -0700 Date: Wed, 10 Jun 2026 17:59:32 +0300 From: Andy Shevchenko To: Kaitao Cheng Cc: Andrew Morton , Petr Mladek , Steven Rostedt , Rasmus Villemoes , Sergey Senozhatsky , linux-kernel@vger.kernel.org, Muchun Song , Kaitao Cheng Subject: Re: [PATCH] lib/vsprintf: Make no_hash_pointers take effect early Message-ID: References: <20260610124525.59110-1-kaitao.cheng@linux.dev> Precedence: bulk X-Mailing-List: linux-kernel@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: <20260610124525.59110-1-kaitao.cheng@linux.dev> Organization: Intel Finland Oy - BIC 0357606-4 - c/o Alberga Business Park, 6 krs, Bertel Jungin Aukio 5, 02600 Espoo On Wed, Jun 10, 2026 at 08:45:25PM +0800, Kaitao Cheng wrote: > The no_hash_pointers boot parameter is now handled as an alias for > hash_pointers=never. However, hash_pointers=never only records the > selected mode during early parameter parsing, and no_hash_pointers is > not updated until hash_pointers_finalize() runs later from SLUB init. > > This leaves a window during very early boot where %p output is still > hashed even though the user explicitly requested unhashed pointers with > no_hash_pointers or hash_pointers=never. > > Set no_hash_pointers as soon as the "never" mode is parsed. The later > hash_pointers_finalize() call still keeps the final policy decision in > one place, but explicit requests to disable pointer hashing now take > effect for early boot users too. How is it documented now? And if not documented at all, needs to be. -- With Best Regards, Andy Shevchenko