From: syzbot <syzbot+ed920a72fd23eb735158@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] INFO: task hung in __generic_file_fsync (3)
Date: Thu, 11 Aug 2022 06:24:09 -0700 [thread overview]
Message-ID: <000000000000a9029805e5f71478@google.com> (raw)
In-Reply-To: <20220811103620.2807-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+ed920a72fd23eb735158@syzkaller.appspotmail.com
Tested on:
commit: 200e340f Merge tag 'pull-work.dcache' of git://git.ker..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=16422f53080000
kernel config: https://syzkaller.appspot.com/x/.config?x=a3f4d6985d3164cd
dashboard link: https://syzkaller.appspot.com/bug?extid=ed920a72fd23eb735158
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=16273ac3080000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2022-08-11 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220811103620.2807-1-hdanton@sina.com>
2022-08-11 13:24 ` syzbot [this message]
[not found] <20220814035942.832-1-hdanton@sina.com>
2022-08-14 7:12 ` [syzbot] INFO: task hung in __generic_file_fsync (3) syzbot
[not found] <20220814010408.770-1-hdanton@sina.com>
2022-08-14 6:39 ` syzbot
[not found] <20220813072749.674-1-hdanton@sina.com>
2022-08-13 13:44 ` syzbot
[not found] <20220812112034.2871-1-hdanton@sina.com>
2022-08-12 13:41 ` syzbot
[not found] <20220810223415.2743-1-hdanton@sina.com>
2022-08-11 4:39 ` syzbot
[not found] <20220810221908.2686-1-hdanton@sina.com>
2022-08-11 4:28 ` syzbot
[not found] <20220810110345.2568-1-hdanton@sina.com>
2022-08-10 16:21 ` syzbot
2022-08-10 5:53 syzbot
2022-08-10 23:40 ` Dave Chinner
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=000000000000a9029805e5f71478@google.com \
--to=syzbot+ed920a72fd23eb735158@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