From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-182.mta0.migadu.com (out-182.mta0.migadu.com [91.218.175.182]) (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 485581D86DC for ; Wed, 20 Aug 2025 22:32:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.182 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755729152; cv=none; b=CdXF+OUfvf0GKMMjl7ij3BW28HubdCVhdH6d1UqSCx4Sko9ZuBt36gKtDYnFWm9cWGi2a3lOBhrKoH8d9KBx1DGhgSywvNeT6LTgslP7J2huM7S0aQZ6vPJLRybI9mSdH70kMgwM1qG9tYw7JoDhzJmUggxcTY7T3DNjbFF2cxU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755729152; c=relaxed/simple; bh=N0IRlJS68kXvQ/sl+UPNiKXqYY0HXBsBdYbmkimwi+8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Wj6qV0LvZwBFCtjIFDD7LNxF/QwE21YzTPXEYGGIzdo9yAE6ryOpEg24ukvXvPvFdhJhFUEmLJyjRmdjZbRbBxxOeWGYe9c5JnoNEDd/QCddo0pWH0gEEEWwEHAsW9NYinSAWpKb0a2duK+ZQJNslG+Jk+r0j8YxXj3fbWMTcOw= 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=nhOltoJ4; arc=none smtp.client-ip=91.218.175.182 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="nhOltoJ4" 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=1755729138; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=N0IRlJS68kXvQ/sl+UPNiKXqYY0HXBsBdYbmkimwi+8=; b=nhOltoJ4OlfQcMaKWmmRjWVkN1LWfrmBEr3jVnKVeFjEL0v3Nf6H2CEUH8t+zgW9CNNX8c Gfkq2j6teAdetfJOQQDNE+3LTxJW+W/kyQkUzm6W4VEeS2knQRIkriUxcMmwkGYIEG14wO UUM2k+bTZdvN4tGUhY5/NeR/tQ4nAG4= From: Roman Gushchin To: Kumar Kartikeya Dwivedi Cc: linux-mm@kvack.org, bpf@vger.kernel.org, Suren Baghdasaryan , Johannes Weiner , Michal Hocko , David Rientjes , Matt Bobrowski , Song Liu , Alexei Starovoitov , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 02/14] bpf: mark struct oom_control's memcg field as TRUSTED_OR_NULL In-Reply-To: (Kumar Kartikeya Dwivedi's message of "Wed, 20 Aug 2025 11:17:38 +0200") References: <20250818170136.209169-1-roman.gushchin@linux.dev> <20250818170136.209169-3-roman.gushchin@linux.dev> Date: Wed, 20 Aug 2025 15:32:11 -0700 Message-ID: <87cy8ppqtw.fsf@linux.dev> Precedence: bulk X-Mailing-List: bpf@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT Kumar Kartikeya Dwivedi writes: > On Mon, 18 Aug 2025 at 19:01, Roman Gushchin wrote: >> >> Struct oom_control is used to describe the OOM context. >> It's memcg field defines the scope of OOM: it's NULL for global >> OOMs and a valid memcg pointer for memcg-scoped OOMs. >> Teach bpf verifier to recognize it as trusted or NULL pointer. >> It will provide the bpf OOM handler a trusted memcg pointer, >> which for example is required for iterating the memcg's subtree. >> >> Signed-off-by: Roman Gushchin >> --- > > Acked-by: Kumar Kartikeya Dwivedi Thanks!