From: syzbot <syzbot+67defecaa74f7dd0a5d3@syzkaller.appspotmail.com>
To: edumazet@google.com, jmorris@namei.org, kuba@kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
penguin-kernel@I-love.SAKURA.ne.jp,
penguin-kernel@i-love.sakura.ne.jp, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, takedakn@nttdata.co.jp,
tomoyo-dev-en-owner@lists.osdn.me, tomoyo-dev-en@lists.osdn.me,
vladimir.oltean@nxp.com
Subject: Re: [syzbot] [tomoyo?] INFO: rcu detected stall in security_file_ioctl (8)
Date: Thu, 01 Aug 2024 20:07:03 -0700 [thread overview]
Message-ID: <00000000000023e800061eaa9fea@google.com> (raw)
In-Reply-To: <mailman.7002.1716464964.1888.tomoyo-dev-en@lists.osdn.me>
syzbot suspects this issue was fixed by commit:
commit e634134180885574d1fe7aa162777ba41e7fcd5b
Author: Vladimir Oltean <vladimir.oltean@nxp.com>
Date: Mon May 27 15:39:54 2024 +0000
net/sched: taprio: make q->picos_per_byte available to fill_sched_entry()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16a9066d980000
start commit: 0450d2083be6 Merge tag '6.10-rc-smb-fix' of git://git.samb..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=17ffd15f654c98ba
dashboard link: https://syzkaller.appspot.com/bug?extid=67defecaa74f7dd0a5d3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17109b3f180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10bcb2a4980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net/sched: taprio: make q->picos_per_byte available to fill_sched_entry()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2024-08-02 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7002.1716464964.1888.tomoyo-dev-en@lists.osdn.me>
2024-08-02 3:07 ` syzbot [this message]
2024-08-02 7:21 ` [syzbot] [tomoyo?] INFO: rcu detected stall in security_file_ioctl (8) Eric Dumazet
2024-05-23 11:49 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=00000000000023e800061eaa9fea@google.com \
--to=syzbot+67defecaa74f7dd0a5d3@syzkaller.appspotmail.com \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takedakn@nttdata.co.jp \
--cc=tomoyo-dev-en-owner@lists.osdn.me \
--cc=tomoyo-dev-en@lists.osdn.me \
--cc=vladimir.oltean@nxp.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 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).