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: Tue, 19 Mar 2024 06:22:42 +0000 [thread overview]
Message-ID: <bug-218601-13602-LvqzgibOrV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218601-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218601
--- Comment #6 from Colin (colin.kernel@i-pentest.info) ---
Firstly, apologies for any incorrectness - the commit reference link did not
accept inputs that were 'probably this sha' or similar - it was not meant in
malice or laziness, but admittedly I was very tiered as a result of the
unpredictability of this issue.
I suspect this may actually be dead hardware but it's hard to tell. If somebody
is interested in exploring this issue further feel free to provide instruction
over the next few days, otherwise I'll buy a new motherboard / RMA the
processor if the motherboard does not fix the issue. I value both my and all of
your time, so buying new equipment in the hopes that I'm rid of the problem is
my preference unless there's some burning desire for further exploration.
Here are some facts:
- `stress-ng --class cpu --seq 32` reliably crashes the machine in less than 60
seconds with the error message 'stress-ng: fail: [2701] af-alg: ctr(twofish):
decrypted data different from original data (possible kernel bug)', as well as
other algos (pcbc(fcrypt), cbc(sm4) etc) noting `dd if=/dev/zero` is not
cryptographic. I routinely checksum files with sha and do not notice any
inconsistencies.
- I have tried vanilla kernels inc. 6.0.1 and 6.8, `dd` _seems_ to fail faster
with more recent kernels, but maybe that's just due to a small test sample
size.
- I have been unable to crash Windows using Prime95 (24h) Furmark (24h) nor dd,
nor am I aware of any errors from either tool. Windows install routinely BSOD,
but went away as soon as I switched to a different USB stick both freshly
flashed - it's possible this is related, but it could also be a bad USB.
- The motherboard is an ASUS Prime Z790-P WiFi D4 LGA 1700, the processor a
13900k, I have been experiencing the issue for about 12 months, seemingly it
has become more frequent lately
- I cannot visually see any problems with the motherboard, no bloated
capacitors as far as I can tell.
- I have replaced the RAM, PSU, SSDs (w/ an non-samsung model) and removed all
aux cards, with the exception of onboard wifi6 which cannot be removed
- Memtest86+ was run with my original 128G ram configuration on 2x24h occasions
and did not yield any errors indicating cpu<>memory integrity is not the issue
--
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-19 6:22 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
2024-03-15 16:55 ` bugzilla-daemon
2024-03-19 6:22 ` bugzilla-daemon [this message]
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-LvqzgibOrV@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.