All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 21 Mar 2024 15:07:31 +0000	[thread overview]
Message-ID: <bug-218601-13602-RaA6w7hQmg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218601-13602@https.bugzilla.kernel.org/>

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

Christian Kujau (kernel@nerdbynature.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kernel@nerdbynature.de

--- Comment #10 from Christian Kujau (kernel@nerdbynature.de) ---
> Building the linux kernel was segfaulting at different locations, 
> I ended up building it on another machine.

Not good. Maybe swap/remove some RAM modules. See also:
https://bitwizard.nl/sig11/

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-03-21 15:07 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
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 [this message]
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-RaA6w7hQmg@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.