From: syzbot <syzbot+bed15dbf10294aa4f2ae@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, longman@redhat.com,
penguin-kernel@i-love.sakura.ne.jp,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
willy@infradead.org
Subject: Re: [syzbot] [ntfs3?] INFO: task hung in do_user_addr_fault (3)
Date: Mon, 02 Jan 2023 06:56:24 -0800 [thread overview]
Message-ID: <000000000000ae803005f149272b@google.com> (raw)
In-Reply-To: <20230102094125.3552-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+bed15dbf10294aa4f2ae@syzkaller.appspotmail.com
Tested on:
commit: 88603b6d Linux 6.2-rc2
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1508687c480000
kernel config: https://syzkaller.appspot.com/x/.config?x=8cdb1e7bec4b955a
dashboard link: https://syzkaller.appspot.com/bug?extid=bed15dbf10294aa4f2ae
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=162634e0480000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2023-01-02 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000060d41f05f139aa44@google.com>
2023-01-02 0:54 ` Hillf Danton
2023-01-02 1:40 ` Linus Torvalds
2023-01-02 8:24 ` Tetsuo Handa
2023-01-02 9:41 ` Hillf Danton
2023-01-02 14:05 ` [PATCH] fs/ntfs3: don't hold ni_lock when calling truncate_setsize() Tetsuo Handa
2023-01-02 14:56 ` syzbot [this message]
2023-01-02 15:37 ` [syzbot] [ntfs3?] INFO: task hung in do_user_addr_fault (3) Matthew Wilcox
2023-01-02 5:27 ` Tetsuo Handa
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=000000000000ae803005f149272b@google.com \
--to=syzbot+bed15dbf10294aa4f2ae@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
/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