From: <rsbecker@nexbridge.com>
To: "'Hans Petter Selasky'" <hps@selasky.org>,
"'Michal Suchánek'" <msuchanek@suse.de>
Cc: <git@vger.kernel.org>, <wrights@alrajhibank.com.sa>
Subject: RE: Gitorious should use CRC128 / 256 / 512 instead of SHA-1
Date: Mon, 16 Jan 2023 07:31:10 -0500 [thread overview]
Message-ID: <017801d929a6$6f8271b0$4e875510$@nexbridge.com> (raw)
In-Reply-To: <6a398405-e5f8-0b78-e463-41d79e49e78b@selasky.org>
On January 16, 2023 4:56 AM, Hans Petter Selasky wrote:
>On 1/16/23 10:13, Michal Suchánek wrote:
>> when that data is copied to a new location a new CRC is calculated
>> that can detect an error in that location.
>
>Yes, that is correct, but what is "copying data"? Are you saying that copying data is
>always error free?
Not in all possible computing devices, no. But in certain high-reliability and mission critical systems, there are parity checks and communication mechanisms that verify the integrity of data transfers memory-to-memory, memory-to-register, and over inter-CPU bus, and memory-to-disk-storage checks. The result of a corruption on one of my systems would result in a CPU halt rather than blindly accepting the result, taking the faulty processor offline until the cause is investigated and then reloaded or repaired. This applies to any component, including disks, CLIMs, DMA, and anything else in the architecture.
next prev parent reply other threads:[~2023-01-16 12:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 13:23 Gitorious should use CRC128 / 256 / 512 instead of SHA-1 Hans Petter Selasky
2023-01-14 23:59 ` brian m. carlson
2023-01-15 3:14 ` Junio C Hamano
2023-01-15 10:09 ` demerphq
2023-01-16 7:21 ` Hans Petter Selasky
2023-01-16 7:23 ` Hans Petter Selasky
2023-01-16 12:34 ` rsbecker
2023-01-16 14:01 ` Hans Petter Selasky
2023-01-16 15:06 ` Junio C Hamano
2023-01-15 13:53 ` Michal Suchánek
2023-01-16 7:17 ` Hans Petter Selasky
2023-01-16 9:13 ` Michal Suchánek
2023-01-16 9:55 ` Hans Petter Selasky
2023-01-16 12:31 ` rsbecker [this message]
2023-01-16 14:10 ` Hans Petter Selasky
2023-01-16 19:08 ` Michal Suchánek
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 12:59 Hans Petter Selasky
2023-01-13 13:30 ` Konstantin Khomoutov
2023-01-13 13:39 ` Hans Petter Selasky
2023-01-13 14:21 ` rsbecker
2023-01-13 14:42 ` Hans Petter Selasky
2023-01-13 15:45 ` Konstantin Ryabitsev
2023-01-13 15:50 ` Hans Petter Selasky
2023-01-13 15:56 ` rsbecker
2023-01-13 16:02 ` Hans Petter Selasky
2023-01-13 15:54 ` Hans Petter Selasky
2023-01-13 16:02 ` Konstantin Ryabitsev
2023-01-13 16:06 ` Hans Petter Selasky
2023-01-13 16:18 ` Hans Petter Selasky
2023-01-13 16:36 ` Konstantin Ryabitsev
2023-01-13 16:44 ` Hans Petter Selasky
2023-01-13 16:49 ` Konstantin Ryabitsev
2023-01-13 16:51 ` Hans Petter Selasky
2023-01-13 16:27 ` Konstantin Ryabitsev
2023-01-13 16:30 ` Hans Petter Selasky
2023-01-13 16:35 ` Hans Petter Selasky
2023-01-13 16:41 ` Konstantin Ryabitsev
2023-01-13 16:45 ` Hans Petter Selasky
2023-01-13 15:15 ` Hans Petter Selasky
2023-01-13 17:44 ` Philip Oakley
2023-01-13 15:30 ` Konstantin Khomoutov
2023-01-13 15:39 ` Konstantin Ryabitsev
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='017801d929a6$6f8271b0$4e875510$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=hps@selasky.org \
--cc=msuchanek@suse.de \
--cc=wrights@alrajhibank.com.sa \
/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).