BPF List
 help / color / mirror / Atom feed
From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "HyeongJun An" <sammiee5311@gmail.com>, <olsajiri@gmail.com>
Cc: <bpf@vger.kernel.org>, <simon@swine.de>, <ast@kernel.org>,
	<andrii@kernel.org>, <daniel@iogearbox.net>,
	<martin.lau@kernel.org>, <tj@kernel.org>,
	<yonghong.song@linux.dev>, <stable@vger.kernel.org>,
	<andrii.nakryiko@gmail.com>
Subject: Re: [PATCH bpf v3 1/2] bpf: disable private stack for sleepable programs
Date: Sat, 31 Oct 2026 05:04:22 +0000	[thread overview]
Message-ID: <DMIRF0WAH6DP.1Q88Y58797IJ4@gmail.com> (raw)
In-Reply-To: <20261031011900.1355507-1-sammiee5311@gmail.com>

On Sat Oct 31, 2026 at 1:19 AM UTC, HyeongJun An wrote:
>  		if (!prog->sleepable)
>  			rcu_read_lock();
> +		if (no_preempt)
> +			preempt_disable();

nack.
The models are sending the same broken thing.
Pls teach them to read lore for nacks.

  reply	other threads:[~2026-10-31  5:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-22 22:54 [PATCH bpf v3 0/2] disable private stack for sleepable programs Christian Simon
2026-08-22 22:54 ` [PATCH bpf v3 1/2] bpf: " Christian Simon
2026-08-22 23:10   ` sashiko-bot
2026-08-22 23:46   ` bot+bpf-ci
2026-08-26  1:20   ` Alexei Starovoitov
2026-08-26 13:11     ` Jiri Olsa
2026-08-27 14:56     ` Andrii Nakryiko
2026-08-27 16:35       ` Alexei Starovoitov
2026-08-27 16:40         ` Andrii Nakryiko
2026-08-27 16:55           ` Alexei Starovoitov
2026-08-27 22:32             ` Jiri Olsa
2026-10-30  1:22               ` HyeongJun An
2026-10-30 23:01                 ` Jiri Olsa
2026-10-31  1:19                   ` HyeongJun An
2026-10-31  5:04                     ` Alexei Starovoitov [this message]
2026-08-22 22:54 ` [PATCH bpf v3 2/2] selftests/bpf: verify preemptible uprobes avoid private stack Christian Simon
2026-08-22 23:05   ` sashiko-bot
2026-08-22 23:58   ` bot+bpf-ci

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=DMIRF0WAH6DP.1Q88Y58797IJ4@gmail.com \
    --to=alexei.starovoitov@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=martin.lau@kernel.org \
    --cc=olsajiri@gmail.com \
    --cc=sammiee5311@gmail.com \
    --cc=simon@swine.de \
    --cc=stable@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox