diff options
author | John Hawthorn <john@hawthorn.email> | 2025-08-12 15:22:23 -0700 |
---|---|---|
committer | git <svn-admin@ruby-lang.org> | 2025-08-19 16:30:50 +0000 |
commit | 3ff1ca07bab3603ad2c0744983d5d7b8b9ac3a44 (patch) | |
tree | 634fdd2d1e92c128d6442559de778b135956a039 /tool/colors | |
parent | 6fe4ed507fc517a22d18f1ea77a4b3a3071310e4 (diff) |
Both the X509 store and X509 store context were missing write barriers.
To the callback object being stored in the ex data.
These values were also being stored as an IV, however in Ruby HEAD we're
now storing the IVs for T_DATA (generic IVs) on a separate object. So we
need an additional write barrier.
I believe this was always necessary, because we could have done
incremental marking ahead of compaction, and without the write barrier
the mark function could have been run before @verify_callback was
assigned.
This was detected by wbcheck
https://github.com/ruby/openssl/commit/1fda3a99ef
Diffstat (limited to 'tool/colors')
0 files changed, 0 insertions, 0 deletions