Greg Kroah-Hartman
598cf27219
Link: https://lore.kernel.org/r/20260217200002.683975158@linuxfoundation.org Tested-by: Florian Fainelli <florian.fainelli@broadcom.com> Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com> Tested-by: Peter Schneider <pschneider1968@googlemail.com> Tested-by: Jon Hunter <jonathanh@nvidia.com> Tested-by: Salvatore Bonaccorso <carnil@debian.org> Tested-by: Brett A C Sheffield <bacs@librecast.net> Tested-by: Mark Brown <broonie@kernel.org> Tested-by: Luna Jernberg <droidbittin@gmail.com> Tested-by: Ronald Warsow <rwarsow@gmx.de> Tested-by: Justin M. Forbes <jforbes@fedoraproject.org> Tested-by: Ron Economos <re@w6rz.net> Tested-by: Miguel Ojeda <ojeda@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
43 lines
892 B
Plaintext
43 lines
892 B
Plaintext
C RCU+sync+free
|
|
|
|
(*
|
|
* Result: Never
|
|
*
|
|
* This litmus test demonstrates that an RCU reader can never see a write that
|
|
* follows a grace period, if it did not see writes that precede that grace
|
|
* period.
|
|
*
|
|
* This is a typical pattern of RCU usage, where the write before the grace
|
|
* period assigns a pointer, and the writes following the grace period destroy
|
|
* the object that the pointer used to point to.
|
|
*
|
|
* This is one implication of the RCU grace-period guarantee, which says (among
|
|
* other things) that an RCU read-side critical section cannot span a grace period.
|
|
*)
|
|
|
|
{
|
|
int x = 1;
|
|
int *y = &x;
|
|
int z = 1;
|
|
}
|
|
|
|
P0(int *x, int *z, int **y)
|
|
{
|
|
int *r0;
|
|
int r1;
|
|
|
|
rcu_read_lock();
|
|
r0 = rcu_dereference(*y);
|
|
r1 = READ_ONCE(*r0);
|
|
rcu_read_unlock();
|
|
}
|
|
|
|
P1(int *x, int *z, int **y)
|
|
{
|
|
rcu_assign_pointer(*y, z);
|
|
synchronize_rcu();
|
|
WRITE_ONCE(*x, 0);
|
|
}
|
|
|
|
exists (0:r0=x /\ 0:r1=0)
|