From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 B43A22C86D for ; Sun, 18 Jan 2026 12:17:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768738661; cv=none; b=lVVCHEhCsUBvAwaT9XB373r8TcWn52Ghzf4Qfl8JFEqeDCCWXGiKQ9dER9yuFSats1X5oMlhfbmYMDPnI7NdS6l+pEaexKXNo/rodHlWhsM/9MHQss3MkrHXCvY3UHcDTKNKzXzMN42aAlNVwrvbSfhfC22WEAQ4dSIeZBSUeck= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768738661; c=relaxed/simple; bh=qmv8ORmWnoMxTVCGZbpQws3WnDSwMW0jSLeuj6yOg98=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=BNab2RgVGEYi+F2JBvOp0+ZXC/e51glD2WCdO9Smgs/Ue8mpAihHuDQ92uubMWxE9o1qMme6QFstW55xqa/oQvbTD3QoVxSrhYIjkVo3Ya6t0yvzcdYSmfaDtByt9H0U0TMvAaQsc8rDIZ7qk0U9TfQ0gh9jrcvG/DdorNMA7lE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=c4Jl3OVO; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="c4Jl3OVO" Received: by smtp.kernel.org (Postfix) with ESMTPSA id F31F1C116D0; Sun, 18 Jan 2026 12:17:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768738661; bh=qmv8ORmWnoMxTVCGZbpQws3WnDSwMW0jSLeuj6yOg98=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=c4Jl3OVO8i4mu1TXuQhW1sD/XctkNy7uFszi75HK+aJXhJHpL2KQZr2ANDSkMlQUy PCzDhkSfM1NGk3EsQko9irugSftavEIRviuFThXWk4I1M/Nlrte3sIQp1kDWLdf00K RhRD7/mBnqOs6tV+Qm8UIe8XwSTDlNcESitXWx1Ox0Fl1YfpMR+SirMEveVQZ9PQqA mzZNbQnlcuapCX79UiwV782t3rail8MeDGYsmZ3xY8DJGF3Y0Wd9VTMQJvWTAyy0eQ NJIT/Bz20eAlmVH2Jct+OLTb8Yy2bidlSXNn7smWCVn7FBc3bUKf8+xzw8cLH+Ld/s ZL7gaiciEr3Mw== Date: Sun, 18 Jan 2026 14:17:33 +0200 From: Mike Rapoport To: Pratyush Yadav Cc: Andrew Morton , Alexander Graf , Pasha Tatashin , kexec@lists.infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Samiullah Khawaja , David Matlack , Jason Miu Subject: Re: [PATCH] kho: print which scratch buffer failed to be reserved Message-ID: References: <20260116165416.1262531-1-pratyush@kernel.org> 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: <20260116165416.1262531-1-pratyush@kernel.org> On Fri, Jan 16, 2026 at 04:54:11PM +0000, Pratyush Yadav wrote: > From: "Pratyush Yadav (Google)" > > When scratch area fails to reserve, KHO prints a message indicating > that. But it doesn't say which scratch failed to allocate. This can be > useful information for debugging. Even more so when the failure is hard > to reproduce. > > Along with the current message, also print which exact scratch area > failed to be reserved. > > Signed-off-by: Pratyush Yadav (Google) Reviewed-by: Mike Rapoport (Microsoft) -- Sincerely yours, Mike.