From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216529] [fstests generic/048] BUG: Kernel NULL pointer dereference at 0x00000069, filemap_release_folio+0x88/0xb0
Date: Tue, 27 Sep 2022 18:06:33 +0000 [thread overview]
Message-ID: <bug-216529-13602-BzFrqlSsx4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216529-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216529
--- Comment #3 from Theodore Tso (tytso@mit.edu) ---
On Tue, Sep 27, 2022 at 12:47:02AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216529
>
> Yes, it's reproducible for me, I just reproduced it again on another ppc64le
> (P8) machine [1]. But it's not easy to reproduce by running generic/048
> (maybe
> there's a better way to reproduce it).
Can you give a rough percentage of how often it reproduces? e.g.,
does it reproduces 10% of the time? 50% of the time? 2-3 times after
100 tries, so 2-3%? etc. If it reproduces but rarely, it'll be a lot
harder to try to bisect.
Something perhaps to try is to enable KASAN, since both stack traces
seem to involve a null pointer derference while trying to free
buffers. Maybe that will give us some hints towards the cause....
Thanks,
- Ted
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-09-27 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 11:55 [Bug 216529] New: [fstests generic/048] BUG: Kernel NULL pointer dereference at 0x00000069, filemap_release_folio+0x88/0xb0 bugzilla-daemon
2022-09-26 5:02 ` Theodore Ts'o
2022-09-27 18:10 ` Ritesh Harjani (IBM)
2022-10-10 17:01 ` Ritesh Harjani (IBM)
2022-09-26 5:02 ` [Bug 216529] " bugzilla-daemon
2022-09-27 0:47 ` bugzilla-daemon
2022-09-27 18:06 ` Theodore Ts'o
2022-09-27 18:06 ` bugzilla-daemon [this message]
2022-09-27 18:10 ` bugzilla-daemon
2022-10-10 17:01 ` bugzilla-daemon
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=bug-216529-13602-BzFrqlSsx4@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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).