From: syzbot <syzbot+67e4f16db666b1c8253c@syzkaller.appspotmail.com>
To: a@unstable.cc, adilger.kernel@dilger.ca,
b.a.t.m.a.n@diktynna.open-mesh.org, benh@kernel.crashing.org,
davem@davemloft.net, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
mareklindner@neomailbox.ch, mpe@ellerman.id.au,
muriloo@linux.ibm.com, netdev@vger.kernel.org, paulus@samba.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: Re: WARNING in ext4_da_update_reserve_space
Date: Sat, 04 Apr 2020 15:13:04 -0700 [thread overview]
Message-ID: <0000000000007b5aea05a27e5637@google.com> (raw)
In-Reply-To: <20200404183707.GK45598@mit.edu>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger crash:
Reported-and-tested-by: syzbot+67e4f16db666b1c8253c@syzkaller.appspotmail.com
Tested on:
commit: 54d3adbc ext4: save all error info in save_error_info() an..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
kernel config: https://syzkaller.appspot.com/x/.config?x=4527d1e2fb19fd5c
dashboard link: https://syzkaller.appspot.com/bug?extid=67e4f16db666b1c8253c
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
Note: testing is done by a robot and is best-effort only.
prev parent reply other threads:[~2020-04-04 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 11:02 WARNING in ext4_da_update_reserve_space syzbot
2020-04-02 14:06 ` Murilo Opsfelder Araújo
2020-04-02 14:31 ` Dmitry Vyukov
2020-04-04 18:37 ` Theodore Y. Ts'o
2020-04-04 22:13 ` 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=0000000000007b5aea05a27e5637@google.com \
--to=syzbot+67e4f16db666b1c8253c@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=adilger.kernel@dilger.ca \
--cc=b.a.t.m.a.n@diktynna.open-mesh.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mareklindner@neomailbox.ch \
--cc=mpe@ellerman.id.au \
--cc=muriloo@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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).