All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b0cff308140f79a9c4cb@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [bpf?] WARNING in bpf_bprintf_prepare (3)
Date: Mon, 20 Oct 2025 23:49:14 -0700	[thread overview]
Message-ID: <68f72cea.a70a0220.3bf6c6.0001.GAE@google.com> (raw)
In-Reply-To: <68f6a4c8.050a0220.1be48.0011.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [bpf?] WARNING in bpf_bprintf_prepare (3)
Author: chandna.sahil@gmail.com

#syz test
--- a/net/core/flow_dissector.c
+++ b/net/core/flow_dissector.c
@@ -1021,7 +1021,9 @@ u32 bpf_flow_dissect(struct bpf_prog *prog, struct bpf_flow_dissector *ctx,
                      (int)FLOW_DISSECTOR_F_STOP_AT_ENCAP);
         flow_keys->flags = flags;

+       preempt_disable();
         result = bpf_prog_run_pin_on_cpu(prog, ctx);
+       preempt_enable();

         flow_keys->nhoff = clamp_t(u16, flow_keys->nhoff, nhoff, hlen);
         flow_keys->thoff = clamp_t(u16, flow_keys->thoff,
--
2.50.1

  reply	other threads:[~2025-10-21  6:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 21:08 [syzbot] [bpf?] WARNING in bpf_bprintf_prepare (3) syzbot
2025-10-21  6:49 ` syzbot [this message]
2025-10-21  9:53 ` Forwarded: " syzbot
2025-10-21  9:56 ` syzbot
2025-10-21 16:26 ` syzbot
2025-10-22 16:57 ` Yonghong Song
2025-10-22 18:40   ` Sahil Chandna
2025-10-22 19:56     ` Yonghong Song
2025-10-26 20:05       ` Sahil Chandna
2025-10-28  3:45         ` Yonghong Song
2025-10-28  7:52           ` Sebastian Andrzej Siewior
2025-10-29 11:22           ` Sahil Chandna
2025-10-29 11:28             ` Sebastian Andrzej Siewior
2025-10-29 15:26             ` Yonghong Song
2025-10-30  8:50               ` Tao Chen
2025-10-30 15:52                 ` Yonghong Song
2025-11-03  1:49                   ` Sahil Chandna
2025-11-03  4:39                     ` Yonghong Song

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=68f72cea.a70a0220.3bf6c6.0001.GAE@google.com \
    --to=syzbot+b0cff308140f79a9c4cb@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /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.