From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-171.mta1.migadu.com (out-171.mta1.migadu.com [95.215.58.171]) (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 0D63E1E487 for ; Tue, 2 Sep 2025 22:30:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.171 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756852229; cv=none; b=ewmdj3D+CeD5GZror6GEahwSlgqzQKLkaLxcDc/rGPbuNBl4QiKaETwyAy7oFfC5MDMDYJu0t/lbI9bU6RxVbAuecW8KMMjwcsM92os1nmu4Ga1DdCQQMKf5Plhv1yUA2b9WDIfigj6s2i0nkzR1esrON1x8OT4Die7kzDugf4M= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756852229; c=relaxed/simple; bh=Zu2O/11sa03bmoU53AKoiAUYiDlGKbRK7En5wuIqf8s=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=SkjQ0+By1AAEirnrbB7kfavuFUmb8rxbFZS73J9JaBTi0xhDDy0YzyN1myK8ZEN9GGyfgLux8B7yWkN9RgYPYc8Va2oQifsCgu8KH9TtgMqUOKD1Qk0XddC7ddPpIb/QqtWdEjH6AjdeAcSP7gKQhyie7otb9uIZ52HjzMXAPMY= 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=dFpU6ost; arc=none smtp.client-ip=95.215.58.171 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="dFpU6ost" Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1756852216; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=WcMClNKqF89fyusNx4KAf+ldD0MkJVJrNd35mLcgadc=; b=dFpU6ostNV6afKRbkI0/nNZ1eh0g4spiTyWoAwtlLsAPG6maCYx9BakMeKrqvtwODdfMoG VYQQmhW5IsWl6KjdaRxwnX1U3SYA7577sVMqDFWS/RPsPxZtC4eqdoIpdKX1J77+IZaV2g 6KbVL82VHMnNa3lv2S59vqH/3DiDG/0= Date: Tue, 2 Sep 2025 15:30:04 -0700 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v1 01/14] mm: introduce bpf struct ops for OOM handling To: Roman Gushchin Cc: Alexei Starovoitov , Kumar Kartikeya Dwivedi , linux-mm , bpf , Suren Baghdasaryan , Johannes Weiner , Michal Hocko , David Rientjes , Matt Bobrowski , Song Liu , Alexei Starovoitov , Andrew Morton , LKML References: <20250818170136.209169-1-roman.gushchin@linux.dev> <20250818170136.209169-2-roman.gushchin@linux.dev> <87ms7tldwo.fsf@linux.dev> <1f2711b1-d809-4063-804b-7b2a3c8d933e@linux.dev> <87wm6rwd4d.fsf@linux.dev> <87iki0n4lm.fsf@linux.dev> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Martin KaFai Lau In-Reply-To: <87iki0n4lm.fsf@linux.dev> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 9/2/25 10:31 AM, Roman Gushchin wrote: > Btw, what's the right way to attach struct ops to a cgroup, if there is > one? Add a cgroup_id field to the struct and use it in the .reg() Adding a cgroup id/fd field to the struct bpf_oom_ops will be hard to attach the same bpf_oom_ops to multiple cgroups. > callback? Or there is something better? There is a link_create.target_fd in the "union bpf_attr". The cgroup_bpf_link_attach() is using it as cgroup fd. May be it can be used here also. This will limit it to link attach only. Meaning the SEC(".struct_ops.link") is supported but not the older SEC(".struct_ops"). I think this should be fine.