Your message dated Sat, 19 Nov 2011 09:44:37 +0000
with message-id <[email protected]>
and subject line Bug#641975: Removed package(s) from unstable
has caused the Debian Bug report #534687,
regarding libssl0.9.8: lh_retrieve modifies global data, bug in valgrind or
OpenSSL?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
534687: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534687
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libssl0.9.8
Version: 0.9.8g-15+lenny1
Severity: normal
==27681== Possible data race during write of size 4 at 0x652e2f0 by thread #5
==27681== at 0x5330C84: lh_retrieve (lhash.c:254)
==27681== by 0x52D12E1: def_get_class (ex_data.c:301)
==27681== by 0x52D180A: int_new_ex_data (ex_data.c:404)
==27681== by 0x5318BD7: RSA_new_method (rsa_lib.c:185)
==27681== by 0x531B76C: rsa_cb (rsa_asn1.c:80)
==27681== by 0x534CB42: asn1_item_ex_combine_new (tasn_new.c:177)
==27681== by 0x53501E4: ASN1_item_ex_d2i (tasn_dec.c:399)
==27681== by 0x53502B3: ASN1_item_d2i (tasn_dec.c:134)
==27681== by 0x534863C: d2i_PublicKey (d2i_pu.c:96)
==27681== by 0x534624F: X509_PUBKEY_get (x_pubkey.c:364)
==27681== by 0x5346C07: d2i_PUBKEY (x_pubkey.c:390)
==27681== by 0x40D480: SelectorInfo::Parse(char*) (dkimverify.cpp:1312)
The above is from a helgrind run on my AMD64 system.
void *lh_retrieve(LHASH *lh, const void *data)
{
lh->error=0;
The relevant code from lhash.c is above, it writes to data in the LHASH
structure pointed to by the first parameter.
static EX_CLASS_ITEM *def_get_class(int class_index)
{
CRYPTO_w_lock(CRYPTO_LOCK_EX_DATA);
p = lh_retrieve(ex_data, &d);
The relevant code from ex_data.c is above. It seems that the lock
CRYPTO_LOCK_EX_DATA will protect the data, so maybe valgrind is getting this
wrong. Valgrind 3.3.1 seemed to miss the CRYPTO_w_lock() type calls, but
I'm using 3.4.1. Maybe this is a bug in valgrind? If you think so then feel
free to reassign it.
--- End Message ---
--- Begin Message ---
Version: 0.9.8o-7+rm
Dear submitter,
as the package openssl098 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see http://bugs.debian.org/641975
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)
--- End Message ---
