From: syzbot <syzbot+8ee0140c3f5eab8a8d4f@syzkaller.appspotmail.com>
To: amir73il@gmail.com, brauner@kernel.org,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] INFO: rcu detected stall in wait4 (4)
Date: Thu, 12 Oct 2023 20:44:27 -0700 [thread overview]
Message-ID: <00000000000093a958060790df91@google.com> (raw)
In-Reply-To: <000000000000648bb80600bccb40@google.com>
syzbot suspects this issue was fixed by commit:
commit 8542f1712074f070ae90b64e6082d10d8e912e32
Author: Amir Goldstein <amir73il@gmail.com>
Date: Mon Oct 2 10:04:45 2023 +0000
ovl: fix file reference leak when submitting aio
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=131df329680000
start commit: 9d23aac8a85f Merge branch 'net-sched-fixes-for-sch_qfq'
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=2a211c03cef60366
dashboard link: https://syzkaller.appspot.com/bug?extid=8ee0140c3f5eab8a8d4f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1014d574a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173e5deca80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ovl: fix file reference leak when submitting aio
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-10-13 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 6:12 [syzbot] [kernel?] INFO: rcu detected stall in wait4 (4) syzbot
2023-10-13 3:44 ` syzbot [this message]
[not found] <20231013111054.1411-1-hdanton@sina.com>
2023-10-13 11:33 ` syzbot
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=00000000000093a958060790df91@google.com \
--to=syzbot+8ee0140c3f5eab8a8d4f@syzkaller.appspotmail.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=netdev@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.