netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+9767c7ed68b95cfa69e6@syzkaller.appspotmail.com>
To: alexei.starovoitov@gmail.com, andrii@kernel.org, ast@kernel.org,
	 bpf@vger.kernel.org, charmitro@posteo.net, daniel@iogearbox.net,
	 davem@davemloft.net, eddyz87@gmail.com, edumazet@google.com,
	 haoluo@google.com, horms@kernel.org, jiayuan.chen@linux.dev,
	 john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
	 kuba@kernel.org, linux-kernel@vger.kernel.org,
	 linux-kselftest@vger.kernel.org, martin.lau@linux.dev,
	mykolal@fb.com,  netdev@vger.kernel.org, pabeni@redhat.com,
	sdf@fomichev.me, shuah@kernel.org,  song@kernel.org,
	syzkaller-bugs@googlegroups.com, tj@kernel.org,
	 yangfeng@kylinos.cn, yonghong.song@linux.dev
Subject: Re: [syzbot] [net?] WARNING: suspicious RCU usage in corrupted (3)
Date: Mon, 08 Sep 2025 13:12:03 -0700	[thread overview]
Message-ID: <68bf3893.050a0220.192772.0885.GAE@google.com> (raw)
In-Reply-To: <683428c8.a70a0220.29d4a0.0802.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 7f12c33850482521c961c5c15a50ebe9b9a88d1e
Author: Charalampos Mitrodimas <charmitro@posteo.net>
Date:   Wed Jun 11 17:20:43 2025 +0000

    net, bpf: Fix RCU usage in task_cls_state() for BPF programs

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13745562580000
start commit:   079e5c56a5c4 bpf: Fix error return value in bpf_copy_from_..
git tree:       bpf-next
kernel config:  https://syzkaller.appspot.com/x/.config?x=c6c517d2f439239
dashboard link: https://syzkaller.appspot.com/bug?extid=9767c7ed68b95cfa69e6
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=114915f4580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15566170580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: net, bpf: Fix RCU usage in task_cls_state() for BPF programs

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  reply	other threads:[~2025-09-08 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26  8:39 [syzbot] [net?] WARNING: suspicious RCU usage in corrupted (3) syzbot
2025-09-08 20:12 ` syzbot [this message]
2025-09-14 23:37   ` Charalampos Mitrodimas

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=68bf3893.050a0220.192772.0885.GAE@google.com \
    --to=syzbot+9767c7ed68b95cfa69e6@syzkaller.appspotmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=charmitro@posteo.net \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=horms@kernel.org \
    --cc=jiayuan.chen@linux.dev \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tj@kernel.org \
    --cc=yangfeng@kylinos.cn \
    --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;
as well as URLs for NNTP newsgroup(s).