From: Rafael David Tinoco <rafaeldtinoco@ubuntu.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ebiggers3@gmail.com, adilger.kernel@dilger.ca,
bot+eb13811afcefe99cfe45081054e7883f569f949d@syzkaller.appspotmail.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: ppc64el kernel access of bad area (ext4_htree_store_dirent->rb_insert_color)
Date: Thu, 12 Dec 2019 09:25:32 -0300 [thread overview]
Message-ID: <2c227a55-5465-e264-dfb8-5ad49412df69@ubuntu.com> (raw)
In-Reply-To: <20191210020130.GA61323@mit.edu>
>> It looks like the same stacktrace that was reported in this thread. This has
>> been reported to ppc64el AND we got a reproducer (ocfs2-tools autopkgtests).
> Can you share your reproducer? Is it a super-simple reproducer that
> doesn't require a complex setup and which can be triggered in some
> kind of virtual machine (under KVM, etc.)?
Yep, its the autopkgtests (debian/tests/*) from ocfs2-tools in bare
metal ppc64el. A bunch of "mkfs.ocfs2, fsck.ocfs2, debugfs.ocfs2,
mount.ocfs2" commands testing package. I got access to same HW that
generated the trace, I'll generate a kdump and share more data soon.
prev parent reply other threads:[~2019-12-12 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <94eb2c1170ce36bd770560ad6d3a@google.com>
2017-12-19 21:59 ` BUG: unable to handle kernel NULL pointer dereference in rb_insert_color Eric Biggers
2017-12-20 7:50 ` Dmitry Vyukov
2017-12-20 7:59 ` Eric Biggers
2017-12-20 8:05 ` Dmitry Vyukov
2018-01-30 21:43 ` Eric Biggers
2019-12-09 13:29 ` ppc64el kernel access of bad area (ext4_htree_store_dirent->rb_insert_color) Rafael David Tinoco
2019-12-09 13:46 ` Dmitry Vyukov
2019-12-10 2:01 ` Theodore Y. Ts'o
2019-12-12 12:25 ` Rafael David Tinoco [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=2c227a55-5465-e264-dfb8-5ad49412df69@ubuntu.com \
--to=rafaeldtinoco@ubuntu.com \
--cc=adilger.kernel@dilger.ca \
--cc=bot+eb13811afcefe99cfe45081054e7883f569f949d@syzkaller.appspotmail.com \
--cc=ebiggers3@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).