2021-07-30 08:22:30 -05:00
|
|
|
#
|
|
|
|
# This file is part of the LibreOffice project.
|
|
|
|
#
|
|
|
|
# This Source Code Form is subject to the terms of the Mozilla Public
|
|
|
|
# License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
|
|
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
|
|
|
|
#
|
|
|
|
|
|
|
|
# Use via environment variable TSAN_OPTIONS=suppressions=.../tsan-suppress.txt
|
|
|
|
|
|
|
|
# There looks to be a lock ordering problem here, but I can't see how it could
|
|
|
|
# actually be hit in practice.
|
|
|
|
deadlock:cppuhelper::ServiceManager::disposing()
|
|
|
|
deadlock:cppuhelper::ServiceManager::loadImplementation
|
2023-01-23 08:01:30 -06:00
|
|
|
deadlock:AffineBridge::v_callInto_v
|
2021-07-30 08:22:30 -05:00
|
|
|
|
2022-08-11 05:13:39 -05:00
|
|
|
# Ignore stuff in external DBUS library.
|
|
|
|
# Some kind of dbus lock issue when we call it from psp::CUPSManager.
|
2021-07-30 08:22:30 -05:00
|
|
|
deadlock:_dbus_lock
|
2023-12-06 06:24:20 -06:00
|
|
|
race:g_dbus_connection_signal_unsubscribe
|
|
|
|
race:g_path_get_basename
|
|
|
|
race:g_date_time_format_iso8601
|
2021-07-30 08:22:30 -05:00
|
|
|
|
2022-08-11 05:13:39 -05:00
|
|
|
# inside an assert so I don't care.
|
2021-07-30 08:22:30 -05:00
|
|
|
race:cppu::OWeakConnectionPoint::acquire
|
|
|
|
race:AffineBridge::v_enter
|
|
|
|
race:__vsnprintf_chk
|
|
|
|
|
|
|
|
# right now, I'm not interested in deadlocks at all, too many false+
|
|
|
|
deadlock:
|
|
|
|
|
2022-03-01 03:09:49 -06:00
|
|
|
# This is checking SAL_STRING_IS_STATIC, which is safe because that is written at compile time.
|
|
|
|
# Depending on the optimisation/debug level, the call stack may have different leaves, hence
|
|
|
|
# specifying this in more than one way.
|
2021-07-30 08:22:30 -05:00
|
|
|
race:rtl::str::acquire<_rtl_uString>
|
|
|
|
race:rtl::str::release<_rtl_uString>
|
2022-03-01 03:09:49 -06:00
|
|
|
race:rtl_uString_acquire
|
|
|
|
race:rtl_uString_release
|
|
|
|
race:rtl_uString_assign
|
2021-07-30 08:22:30 -05:00
|
|
|
|
|
|
|
# I've convinced myself this is a false+, caused by ping-ponging the buffer between two
|
2022-08-11 05:13:39 -05:00
|
|
|
# threads, but I might be wrong.
|
2021-07-30 08:22:30 -05:00
|
|
|
race:XBufferedThreadedStream::getNextBlock
|
|
|
|
|
2022-08-11 05:13:39 -05:00
|
|
|
# I am not interested in stuff the embedded JVM does.
|
2021-07-30 08:22:30 -05:00
|
|
|
race:libjvm.so
|
2021-08-02 07:18:56 -05:00
|
|
|
|
|
|
|
# I think this is OK, because at this point we are doing
|
|
|
|
# if (nRefCount > 1)
|
|
|
|
# and we know from our callers that the refcount must be at least one
|
2022-08-11 05:13:39 -05:00
|
|
|
# so there is no failure mode.
|
2021-08-02 07:18:56 -05:00
|
|
|
race:ireallocSequence
|
|
|
|
|
2021-08-03 05:57:22 -05:00
|
|
|
# TODO There appears to be a race here, initialising the
|
2021-08-02 07:18:56 -05:00
|
|
|
# ::com::sun::star::uno::Sequence< T >::s_pType
|
|
|
|
# field. But no idea at all how to fix it.
|
|
|
|
race:cppu::getTypeFavourUnsigned
|
|
|
|
|
2021-08-05 03:07:38 -05:00
|
|
|
|
2022-08-11 05:13:39 -05:00
|
|
|
# This is all inside GIO/Glib, no idea what it is doing.
|
2021-08-05 03:07:38 -05:00
|
|
|
#
|
|
|
|
race:slab_allocator_alloc_chunk
|
|
|
|
race:g_source_destroy_internal
|
|
|
|
race:g_source_unref_internal
|
|
|
|
race:g_task_finalize
|
2021-12-27 14:44:46 -06:00
|
|
|
race:g_socket_send_message_with_timeout
|
2022-08-11 05:13:39 -05:00
|
|
|
race:g_idle_source_new
|
2022-09-02 02:40:30 -05:00
|
|
|
race:g_slice_alloc0
|
2023-10-30 05:09:39 -05:00
|
|
|
race:g_str_has_suffix
|
|
|
|
race:g_str_equal
|
|
|
|
race:g_strsplit
|
|
|
|
race:g_variant_store
|
2023-01-23 08:01:30 -06:00
|
|
|
|
|
|
|
# Python build, lock order inversion
|
|
|
|
deadlock:take_gil
|
2023-08-25 08:33:45 -05:00
|
|
|
|
|
|
|
# Not interested in deadlock issues when they involve the shutdown path
|
|
|
|
# - the shutdown path is special, so if we see a lock-ordering here that conflicts with
|
|
|
|
# a "normal" lock-ordering path, that is highly unlikely to result in a real issue.
|
|
|
|
deadlock:DeInitVCL
|
|
|
|
|
|
|
|
# Sometimes tsan will report data-races in these, who knows why, they should be thread-safe
|
|
|
|
race:malloc
|
|
|
|
race:free
|
|
|
|
race:close
|
|
|
|
|
|
|
|
# There is a lock-cycle here, together with the mutexes acquired in
|
|
|
|
# SvtSysLocaleOptions::SvtSysLocaleOptions
|
|
|
|
# SvtSysLocale::SvtSysLocale
|
|
|
|
# but I can't see how it could lead to a problem in practice
|
|
|
|
deadlock:ItemHolder1::impl_addItem
|
|
|
|
|
2023-08-25 11:51:46 -05:00
|
|
|
# ignore warning about nRefCount in sal_Sequence.
|
2023-08-25 08:33:45 -05:00
|
|
|
# <sberg> noelgrandin, we generally assume that sal_Int32 is small enough, and hardware sane enough,
|
|
|
|
# that reading it will always give a sane value, i.e., if the read happens in parallel with a write,
|
|
|
|
# the read produces either the old, original value, or the newly written one.
|
|
|
|
race:cppu::createEmptySequence
|
|
|
|
race:uno_type_sequence_reference2One
|