From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 218601] Regression - dd if=/dev/zero of=/zero causes shift-out-of-bounds && NULL pointer dereference, address: 0000000000000003
Date: Fri, 15 Mar 2024 10:18:52 +0000 [thread overview]
Message-ID: <bug-218601-13602-4CRFIjESSu@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218601-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218601
Artem S. Tashkinov (aros@gmx.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Bisected commit-id|326e1c208f3f24d14b93f910b8a |
|e32c94923d22c |
--- Comment #4 from Artem S. Tashkinov (aros@gmx.com) ---
I'm not an expert bug your backtrace looks weird. Please run memtest86 or
memtest86+ for an hour or two.
https://www.memtest86.com/download.htm
https://github.com/memtest86plus/memtest86plus/releases
I'm also removing the bisected ID because it doesn't look like it has anything
to do with this issue.
You don't just copy random stuff from other bug reports which look similar to
yours. You actually bisect and provide the full bisect history.
Ubuntu 22.10 comes with kernel Kernel 5.19.
Ubuntu 23.10 comes with kernel Kernel 6.5.
That's a very large regression window. And then you can only bisect on vanilla
kernels, not Ubuntu ones. First compile and make sure 5.19 absolutely works for
you. Then try consecutive kernels one by one. If you hit the issue, then you
will have just two kernel releases to work with, instead of trying to find the
regressions between two very distant kernels.
https://docs.kernel.org/admin-guide/bug-bisect.html
Best of luck.
--
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:[~2024-03-15 10:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-218601-13602@https.bugzilla.kernel.org/>
2024-03-15 10:04 ` [Bug 218601] Regression - dd if=/dev/zero of=/zero causes shift-out-of-bounds && NULL pointer dereference, address: 0000000000000003 bugzilla-daemon
2024-03-15 10:07 ` bugzilla-daemon
2024-03-15 10:18 ` bugzilla-daemon [this message]
2024-03-15 16:55 ` bugzilla-daemon
2024-03-19 6:22 ` bugzilla-daemon
2024-03-19 15:08 ` bugzilla-daemon
2024-03-21 5:20 ` bugzilla-daemon
2024-03-21 5:20 ` bugzilla-daemon
2024-03-21 15:07 ` bugzilla-daemon
2024-03-21 16:20 ` 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-218601-13602-4CRFIjESSu@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 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.