Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <000000000000d1663705ee97d4d7@google.com> <20221129203054.GF3600936@dread.disaster.area>
In-Reply-To: <20221129203054.GF3600936@dread.disaster.area>
From:   Andreas Gruenbacher <agruenba@redhat.com>
Date:   Sun, 4 Dec 2022 17:36:49 +0100
Message-ID: <CAHc6FU4OhgPsgBGZjKEma8Qt0=HnfkTWL2mWEXCrJEi4P4SnLQ@mail.gmail.com>
Subject: Re: [Cluster-devel] [syzbot] WARNING in iomap_read_inline_data
To:     Dave Chinner <david@fromorbit.com>
Cc:     syzbot <syzbot+7bb81dfa9cda07d9cd9d@syzkaller.appspotmail.com>,
        linux-xfs@vger.kernel.org, cluster-devel@redhat.com,
        djwong@kernel.org, syzkaller-bugs@googlegroups.com,
        linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Tue, Nov 29, 2022 at 9:31 PM Dave Chinner <david@fromorbit.com> wrote:
> Looks like something to do with the gfs2 inline data functionality -
> syzbot probably corrupted the resource index inode given the
> gfs2_fill_super() context.

Hmm, interesting. We're not checking the size of inline (stuffed)
inodes when reading them from disk in gfs2_dinode_in(). I'll fix that.

Thanks,
Andreas