From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 644EF38537BC; Tue, 13 Dec 2022 21:53:33 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 644EF38537BC DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670968413; bh=8NfXealT+N2Ds/toyCOJCWpPkCysrv5pD12tqg0LSVg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=M8C32/MH1Oww0WSK56iA1jkXCVtF3VOyYmHBU1TCEXNzGW7XluDXv5ezcwjQymwvh 6SJuhS0WTzE/QCLX/cf/7o/ZBVHADa5q5AN29lNKCjPih8t4kZ5M1NOHW6ojQ6typL MJ+P5ysfWlqOyW1YIaWl9qAwU+uX4U5W7+A/kZtI= From: "bhaskar at yottadb dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/29863] Segmentation fault in memcmp-sse2.S if memory contents can concurrently change Date: Tue, 13 Dec 2022 21:53:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: bhaskar at yottadb dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29863 --- Comment #12 from K.S. Bhaskar --- While I can't speak to the other databases, the YottaDB code base goes back much further than 25 years. Under the name GT.M, it first saw live producti= on use in 1986. Its use of optimistic concurrency control was inspired by Kung= & Robinson's seminal paper (https://www.eecs.harvard.edu/~htk/publication/1981-tods-kung-robinson.pdf)= . I personally know the original author of the code, as well as someone who has worked on the code base since the mid 1980s. In addition to those mentioned= by Narayanan, the code has over the decades run on several other CPU architect= ures and operating systems. I hope this suffices as a use case. --=20 You are receiving this mail because: You are on the CC list for the bug.=