From: syzbot <syzbot+4d99a966fd74bdeeec36@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, bagasdotme@gmail.com,
ebiggers@kernel.org, guohanjun@huawei.com, jack@suse.cz,
johnny.chenyi@huawei.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, liuyongqiang13@huawei.com,
miaoxie@huawei.com, patchwork@huawei.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
weiyongjun1@huawei.com, yanaijie@huawei.com, yebin10@huawei.com,
yebin@huaweicloud.com, yuehaibing@huawei.com
Subject: Re: [syzbot] WARNING in ext4_expand_extra_isize_ea
Date: Thu, 02 Feb 2023 04:10:23 -0800 [thread overview]
Message-ID: <000000000000168a9205f3b6738f@google.com> (raw)
In-Reply-To: <000000000000befd1d05eeb5af30@google.com>
syzbot suspects this issue was fixed by commit:
commit cc12a6f25e07ed05d5825a1664b67a970842b2ca
Author: Ye Bin <yebin10@huawei.com>
Date: Thu Dec 8 02:32:31 2022 +0000
ext4: allocate extended attribute value in vmalloc area
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14e7b9a5480000
start commit: 644e9524388a Merge tag 'for-v6.1-rc' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8d01b6e3197974dd
dashboard link: https://syzkaller.appspot.com/bug?extid=4d99a966fd74bdeeec36
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12f49603880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163dfb9b880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ext4: allocate extended attribute value in vmalloc area
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-02-02 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 20:09 [syzbot] WARNING in ext4_expand_extra_isize_ea syzbot
2023-02-02 12:10 ` syzbot [this message]
2023-02-02 13:09 ` Aleksandr Nogikh
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=000000000000168a9205f3b6738f@google.com \
--to=syzbot+4d99a966fd74bdeeec36@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=bagasdotme@gmail.com \
--cc=ebiggers@kernel.org \
--cc=guohanjun@huawei.com \
--cc=jack@suse.cz \
--cc=johnny.chenyi@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyongqiang13@huawei.com \
--cc=miaoxie@huawei.com \
--cc=patchwork@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=weiyongjun1@huawei.com \
--cc=yanaijie@huawei.com \
--cc=yebin10@huawei.com \
--cc=yebin@huaweicloud.com \
--cc=yuehaibing@huawei.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