From: syzbot <syzbot+b9564ba6e8e00694511b@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: rcu detected stall in ext4_file_write_iter (6)
Date: Wed, 08 Feb 2023 23:34:18 -0800 [thread overview]
Message-ID: <0000000000009b1e8a05f43f68a5@google.com> (raw)
In-Reply-To: <20230209072740.2224-1-hdanton@sina.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
kernel/time/tick-sched.c:1498:40: error: expected ')' before ';' token
kernel/time/tick-sched.c:1498:2: error: too few arguments to function 'hrtimer_forward_now'
kernel/time/tick-sched.c:1500:25: error: expected ';' before '}' token
kernel/time/tick-sched.c:1501:1: error: control reaches end of non-void function [-Werror=return-type]
Tested on:
commit: 4fafd969 Add linux-next specific files for 20230203
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
dashboard link: https://syzkaller.appspot.com/bug?extid=b9564ba6e8e00694511b
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=17347093480000
next parent reply other threads:[~2023-02-09 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230209072740.2224-1-hdanton@sina.com>
2023-02-09 7:34 ` syzbot [this message]
[not found] <20230210065053.2385-1-hdanton@sina.com>
2023-02-10 7:16 ` [syzbot] INFO: rcu detected stall in ext4_file_write_iter (6) syzbot
[not found] <20230209073104.2276-1-hdanton@sina.com>
2023-02-09 7:50 ` syzbot
[not found] <20230209061936.2127-1-hdanton@sina.com>
2023-02-09 7:16 ` syzbot
[not found] <20230209010659.2012-1-hdanton@sina.com>
2023-02-09 6:07 ` syzbot
[not found] <20230208132556.1881-1-hdanton@sina.com>
2023-02-08 14:15 ` syzbot
2023-02-08 10:37 syzbot
2023-02-09 22:25 ` Thomas Gleixner
2023-02-13 22:28 ` John Stultz
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=0000000000009b1e8a05f43f68a5@google.com \
--to=syzbot+b9564ba6e8e00694511b@syzkaller.appspotmail.com \
--cc=hdanton@sina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox