From: syzbot <syzbot+a98f21ebda0a437b04d7@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com,
torvalds@linux-foundation.org
Subject: Re: [syzbot] [ntfs3?] WARNING in attr_data_get_block (2)
Date: Tue, 30 May 2023 21:14:27 -0700 [thread overview]
Message-ID: <00000000000040020d05fcf58ebf@google.com> (raw)
In-Reply-To: <000000000000030b7e05f7b9ac32@google.com>
syzbot suspects this issue was fixed by commit:
commit 68674f94ffc9dddc45e7733963ecc35c5eda9efd
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Sat Apr 15 18:47:06 2023 +0000
x86: don't use REP_GOOD or ERMS for small memory copies
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12de3271280000
start commit: ffe78bbd5121 Merge tag 'xtensa-20230327' of https://github..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9c35b3803e5ad668
dashboard link: https://syzkaller.appspot.com/bug?extid=a98f21ebda0a437b04d7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=139dca3ec80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a55a35c80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: x86: don't use REP_GOOD or ERMS for small memory copies
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-05-31 4:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 13:41 [syzbot] [ntfs3?] WARNING in attr_data_get_block (2) syzbot
2023-03-30 16:25 ` syzbot
2023-05-31 4:14 ` syzbot [this message]
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=00000000000040020d05fcf58ebf@google.com \
--to=syzbot+a98f21ebda0a437b04d7@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).