All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+693a483dd6ac06c62b09@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bigeasy@linutronix.de,
	bsegall@google.com,  dietmar.eggemann@arm.com,
	edumazet@google.com, juri.lelli@redhat.com,
	 kerneljasonxing@gmail.com, kuba@kernel.org,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	mgorman@suse.de, mingo@redhat.com, netdev@vger.kernel.org,
	 pabeni@redhat.com, peterz@infradead.org, rostedt@goodmis.org,
	 syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
	 vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [syzbot] [mm?] INFO: rcu detected stall in sys_pipe2 (2)
Date: Fri, 26 Dec 2025 08:43:01 -0800	[thread overview]
Message-ID: <694ebb15.050a0220.35954c.0076.GAE@google.com> (raw)
In-Reply-To: <6730d6bd.050a0220.1fb99c.0139.GAE@google.com>

syzbot suspects this issue was fixed by commit:

commit 66951e4860d3c688bfa550ea4a19635b57e00eca
Author: Peter Zijlstra <peterz@infradead.org>
Date:   Mon Jan 13 12:50:11 2025 +0000

    sched/fair: Fix update_cfs_group() vs DELAY_DEQUEUE

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16c6eb92580000
start commit:   9268abe611b0 Merge branch 'net-lan969x-add-rgmii-support'
git tree:       net-next
kernel config:  https://syzkaller.appspot.com/x/.config?x=b087c24b921cdc16
dashboard link: https://syzkaller.appspot.com/bug?extid=693a483dd6ac06c62b09
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=16e7c2f8580000

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

#syz fix: sched/fair: Fix update_cfs_group() vs DELAY_DEQUEUE

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


      parent reply	other threads:[~2025-12-26 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 15:52 [syzbot] [mm?] INFO: rcu detected stall in sys_pipe2 (2) syzbot
2024-12-25  0:22 ` syzbot
2025-01-07 23:18 ` syzbot
2025-12-26 16:43 ` syzbot [this message]

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=694ebb15.050a0220.35954c.0076.GAE@google.com \
    --to=syzbot+693a483dd6ac06c62b09@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=edumazet@google.com \
    --cc=juri.lelli@redhat.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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.