All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Khawar Ahemad <ahemadkhawar123@gmail.com>, bpf@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ast@kernel.org,
	daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
	jiayuan.chen@linux.dev, emil@etsalapatis.com
Subject: Re: [PATCH bpf-next v6 0/4] bpf: arena: handle memory.max on fault-in with reclaim/OOM
Date: Tue, 25 Aug 2026 17:55:04 +0800	[thread overview]
Message-ID: <95517552-a0aa-430a-807c-be3299e33dcf@linux.dev> (raw)
In-Reply-To: <20260825094955.83240-1-ahemadkhawar123@gmail.com>


On 8/25/26 5:49 PM, Khawar Ahemad wrote:
> This series fixes an issue where accessing a valid BPF arena page under
> memory pressure (hitting a cgroup's memory.max limit) incorrectly results
> in a SIGSEGV crash instead of invoking memory reclaim or the memcg OOM
> killer.
>
> Problem:


Hi Khawar,

Just curious — is there a reason you're sending the same patchset 
multiple times? It will cause flooding on the list.


  parent reply	other threads:[~2026-08-25  9:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25  9:49 [PATCH bpf-next v6 0/4] bpf: arena: handle memory.max on fault-in with reclaim/OOM Khawar Ahemad
2026-08-25  9:49 ` [PATCH bpf-next v6 1/4] bpf: Add a sleepable page allocator for map memory Khawar Ahemad
2026-08-25 10:11   ` sashiko-bot
2026-08-25 10:22   ` Khawar Ahemad
2026-08-25 10:32   ` bot+bpf-ci
2026-08-25  9:49 ` [PATCH bpf-next v6 2/4] bpf: arena: allocate the fault-in page outside the lock Khawar Ahemad
2026-08-25 10:32   ` bot+bpf-ci
2026-08-25  9:49 ` [PATCH bpf-next v6 3/4] selftests/bpf: Add read_cgroup_file() to cgroup_helpers Khawar Ahemad
2026-08-25  9:49 ` [PATCH bpf-next v6 4/4] selftests/bpf: Add a test for arena fault-in under memory.max Khawar Ahemad
2026-08-25 10:32   ` bot+bpf-ci
2026-08-25 10:43   ` Khawar Ahemad
2026-08-25 11:19     ` Jiayuan Chen
2026-08-25 12:23       ` Kumar Kartikeya Dwivedi
2026-08-25 11:28   ` Khawar Ahemad
2026-08-25  9:55 ` Jiayuan Chen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-08-25  9:19 [PATCH bpf-next v6 0/4] bpf: arena: handle memory.max on fault-in with reclaim/OOM Khawar Ahemad
2026-08-25  9:16 Khawar Ahemad

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95517552-a0aa-430a-807c-be3299e33dcf@linux.dev \
    --to=jiayuan.chen@linux.dev \
    --cc=ahemadkhawar123@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.