All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: syzbot <syzbot+67e4f16db666b1c8253c@syzkaller.appspotmail.com>
Cc: 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
Subject: Re: WARNING in ext4_da_update_reserve_space
Date: Sat, 4 Apr 2020 14:37:07 -0400	[thread overview]
Message-ID: <20200404183707.GK45598@mit.edu> (raw)
In-Reply-To: <0000000000008c5a4605a24cbb16@google.com>

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev

I'm curious why this is only showing up as failing on next-next.
Let's see if it fails on the ext4.git tree.

From the bisect logs syzbot is able to repro on all of v5.x and
v4.20.0.  However, I'm not able to repro it using kvm with either
v5.6-rc4 or the tip of the ext4 git tree.  So let's see what syzbot
can do with the tip of the dev tree.

						- Ted

WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: syzbot <syzbot+67e4f16db666b1c8253c@syzkaller.appspotmail.com>
Cc: mareklindner@neomailbox.ch, sw@simonwunderlich.de,
	muriloo@linux.ibm.com, a@unstable.cc,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
	b.a.t.m.a.n@diktynna.open-mesh.org, netdev@vger.kernel.org,
	adilger.kernel@dilger.ca, paulus@samba.org,
	linux-ext4@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	davem@davemloft.net
Subject: Re: WARNING in ext4_da_update_reserve_space
Date: Sat, 4 Apr 2020 14:37:07 -0400	[thread overview]
Message-ID: <20200404183707.GK45598@mit.edu> (raw)
In-Reply-To: <0000000000008c5a4605a24cbb16@google.com>

#syz test https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev

I'm curious why this is only showing up as failing on next-next.
Let's see if it fails on the ext4.git tree.

From the bisect logs syzbot is able to repro on all of v5.x and
v4.20.0.  However, I'm not able to repro it using kvm with either
v5.6-rc4 or the tip of the ext4 git tree.  So let's see what syzbot
can do with the tip of the dev tree.

						- Ted

  parent reply	other threads:[~2020-04-04 18:38 UTC|newest]

Thread overview: 8+ 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:06   ` Murilo Opsfelder Araújo
2020-04-02 14:31   ` Dmitry Vyukov
2020-04-02 14:31     ` Dmitry Vyukov
2020-04-04 18:37 ` Theodore Y. Ts'o [this message]
2020-04-04 18:37   ` Theodore Y. Ts'o
2020-04-04 22:13   ` syzbot

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=20200404183707.GK45598@mit.edu \
    --to=tytso@mit.edu \
    --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=syzbot+67e4f16db666b1c8253c@syzkaller.appspotmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.