linux-ext4 - [Bug 218601] Regression - dd if=/dev/zero of=/zero causes shift-out-of-bounds && NULL pointer dereference, address: 0000000000000003

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <bug-218601-13602-4CRFIjESSu@https.bugzilla.kernel.org/>
Date: Fri, 15 Mar 2024 10:18:52 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 218601] Regression - dd if=/dev/zero of=/zero causes
 shift-out-of-bounds &&  NULL pointer dereference, address: 0000000000000003

https://bugzilla.kernel.org/show_bug.cgi?id=218601

Artem S. Tashkinov (aros@....com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Bisected commit-id|326e1c208f3f24d14b93f910b8a |
                   |e32c94923d22c               |

--- Comment #4 from Artem S. Tashkinov (aros@....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.