2020-01-18 08:38:21 +00:00
|
|
|
/*
|
2022-05-07 09:59:46 +00:00
|
|
|
* Copyright (c) 2018-2022, Andreas Kling <kling@serenityos.org>
|
2020-01-18 08:38:21 +00:00
|
|
|
*
|
2021-04-22 08:24:48 +00:00
|
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
2020-01-18 08:38:21 +00:00
|
|
|
*/
|
|
|
|
|
2018-10-13 13:41:24 +00:00
|
|
|
#pragma once
|
|
|
|
|
2020-12-29 20:14:21 +00:00
|
|
|
#ifdef KERNEL
|
2022-05-07 09:59:46 +00:00
|
|
|
# include <Kernel/Library/ThreadSafeWeakable.h>
|
2022-01-18 20:21:37 +00:00
|
|
|
#else
|
2022-05-07 09:59:46 +00:00
|
|
|
# include <AK/Assertions.h>
|
|
|
|
# include <AK/Atomic.h>
|
|
|
|
# include <AK/RefCounted.h>
|
|
|
|
# include <AK/RefPtr.h>
|
|
|
|
# include <AK/StdLibExtras.h>
|
2022-01-18 20:21:37 +00:00
|
|
|
# include <sched.h>
|
2018-10-13 13:41:24 +00:00
|
|
|
|
|
|
|
namespace AK {
|
|
|
|
|
2019-05-28 09:53:16 +00:00
|
|
|
template<typename T>
|
|
|
|
class Weakable;
|
|
|
|
template<typename T>
|
|
|
|
class WeakPtr;
|
2018-10-13 13:41:24 +00:00
|
|
|
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
class WeakLink : public RefCounted<WeakLink> {
|
|
|
|
template<typename T>
|
|
|
|
friend class Weakable;
|
|
|
|
template<typename T>
|
|
|
|
friend class WeakPtr;
|
2019-05-28 09:53:16 +00:00
|
|
|
|
2018-10-13 13:41:24 +00:00
|
|
|
public:
|
2022-05-07 10:50:54 +00:00
|
|
|
template<typename T>
|
|
|
|
RefPtr<T> strong_ref() const
|
2022-03-17 17:29:46 +00:00
|
|
|
requires(IsBaseOf<RefCountedBase, T>)
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
{
|
2022-05-07 10:50:54 +00:00
|
|
|
RefPtr<T> ref;
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
|
|
|
|
{
|
2020-12-29 20:14:21 +00:00
|
|
|
if (!(m_consumers.fetch_add(1u << 1, AK::MemoryOrder::memory_order_acquire) & 1u)) {
|
|
|
|
T* ptr = (T*)m_ptr.load(AK::MemoryOrder::memory_order_acquire);
|
|
|
|
if (ptr && ptr->try_ref())
|
2021-04-23 14:46:57 +00:00
|
|
|
ref = adopt_ref(*ptr);
|
2020-12-29 20:14:21 +00:00
|
|
|
}
|
|
|
|
m_consumers.fetch_sub(1u << 1, AK::MemoryOrder::memory_order_release);
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
return ref;
|
|
|
|
}
|
|
|
|
|
|
|
|
template<typename T>
|
|
|
|
T* unsafe_ptr() const
|
|
|
|
{
|
2020-12-29 20:14:21 +00:00
|
|
|
if (m_consumers.load(AK::MemoryOrder::memory_order_relaxed) & 1u)
|
|
|
|
return nullptr;
|
|
|
|
// NOTE: This may return a non-null pointer even if revocation
|
|
|
|
// has been triggered as there is a possible race! But it's "unsafe"
|
|
|
|
// anyway because we return a raw pointer without ensuring a
|
|
|
|
// reference...
|
|
|
|
return (T*)m_ptr.load(AK::MemoryOrder::memory_order_acquire);
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
bool is_null() const
|
|
|
|
{
|
2021-11-06 20:12:16 +00:00
|
|
|
return unsafe_ptr<void>() == nullptr;
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void revoke()
|
|
|
|
{
|
2020-12-29 20:14:21 +00:00
|
|
|
auto current_consumers = m_consumers.fetch_or(1u, AK::MemoryOrder::memory_order_relaxed);
|
2021-02-23 19:42:32 +00:00
|
|
|
VERIFY(!(current_consumers & 1u));
|
2022-01-07 12:04:05 +00:00
|
|
|
// We flagged revocation, now wait until everyone trying to obtain
|
2020-12-29 20:14:21 +00:00
|
|
|
// a strong reference is done
|
|
|
|
while (current_consumers > 0) {
|
2022-01-18 20:21:37 +00:00
|
|
|
sched_yield();
|
2020-12-29 20:14:21 +00:00
|
|
|
current_consumers = m_consumers.load(AK::MemoryOrder::memory_order_acquire) & ~1u;
|
|
|
|
}
|
|
|
|
// No one is trying to use it (anymore)
|
|
|
|
m_ptr.store(nullptr, AK::MemoryOrder::memory_order_release);
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
}
|
2018-10-13 13:41:24 +00:00
|
|
|
|
|
|
|
private:
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
template<typename T>
|
2019-05-28 09:53:16 +00:00
|
|
|
explicit WeakLink(T& weakable)
|
2020-12-29 20:14:21 +00:00
|
|
|
: m_ptr(&weakable)
|
2019-05-28 09:53:16 +00:00
|
|
|
{
|
|
|
|
}
|
2020-12-29 20:14:21 +00:00
|
|
|
mutable Atomic<void*> m_ptr;
|
2022-01-07 12:04:05 +00:00
|
|
|
mutable Atomic<unsigned> m_consumers; // LSB indicates revocation in progress
|
2018-10-13 13:41:24 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
template<typename T>
|
|
|
|
class Weakable {
|
|
|
|
private:
|
|
|
|
class Link;
|
2019-05-28 09:53:16 +00:00
|
|
|
|
2018-10-13 13:41:24 +00:00
|
|
|
public:
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
template<typename U = T>
|
2022-02-13 19:34:11 +00:00
|
|
|
WeakPtr<U> make_weak_ptr() const
|
|
|
|
{
|
|
|
|
return MUST(try_make_weak_ptr<U>());
|
|
|
|
}
|
2022-05-07 09:59:46 +00:00
|
|
|
|
2022-02-13 19:16:21 +00:00
|
|
|
template<typename U = T>
|
|
|
|
ErrorOr<WeakPtr<U>> try_make_weak_ptr() const;
|
2018-10-13 13:41:24 +00:00
|
|
|
|
|
|
|
protected:
|
2021-01-10 23:29:28 +00:00
|
|
|
Weakable() = default;
|
2018-10-13 13:41:24 +00:00
|
|
|
|
|
|
|
~Weakable()
|
|
|
|
{
|
2020-07-04 14:22:32 +00:00
|
|
|
revoke_weak_ptrs();
|
|
|
|
}
|
|
|
|
|
|
|
|
void revoke_weak_ptrs()
|
|
|
|
{
|
2020-12-29 20:14:21 +00:00
|
|
|
if (auto link = move(m_link))
|
|
|
|
link->revoke();
|
2018-10-13 13:41:24 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
private:
|
AK: Make RefPtr, NonnullRefPtr, WeakPtr thread safe
This makes most operations thread safe, especially so that they
can safely be used in the Kernel. This includes obtaining a strong
reference from a weak reference, which now requires an explicit
call to WeakPtr::strong_ref(). Another major change is that
Weakable::make_weak_ref() may require the explicit target type.
Previously we used reinterpret_cast in WeakPtr, assuming that it
can be properly converted. But WeakPtr does not necessarily have
the knowledge to be able to do this. Instead, we now ask the class
itself to deliver a WeakPtr to the type that we want.
Also, WeakLink is no longer specific to a target type. The reason
for this is that we want to be able to safely convert e.g. WeakPtr<T>
to WeakPtr<U>, and before this we just reinterpret_cast the internal
WeakLink<T> to WeakLink<U>, which is a bold assumption that it would
actually produce the correct code. Instead, WeakLink now operates
on just a raw pointer and we only make those constructors/operators
available if we can verify that it can be safely cast.
In order to guarantee thread safety, we now use the least significant
bit in the pointer for locking purposes. This also means that only
properly aligned pointers can be used.
2020-09-29 22:26:13 +00:00
|
|
|
mutable RefPtr<WeakLink> m_link;
|
2018-10-13 13:41:24 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
using AK::Weakable;
|
2022-05-07 09:59:46 +00:00
|
|
|
|
|
|
|
#endif
|