tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: MCLADDREFERENCE() incrementing the wrong ext_refcnt?

To: tech-kern%netbsd.org@localhost
Subject: Re: MCLADDREFERENCE() incrementing the wrong ext_refcnt?
From: Edgar Fuß <ef%math.uni-bonn.de@localhost>
Date: Sun, 31 Mar 2024 21:55:30 +0200

> So I think
>         atomic_inc_uint(&(o)->m_ext.ext_refcnt);                        \
> should really be
>         atomic_inc_uint(&(o)->m_ext_ref->m_ext.ext_refcnt);             \
> which, of course, is the same thing if MEXT_ISEMBEDDED(o) is true.

> Am I getting something wrong?
Self-answer: Yes.
m_ext is m_ext_ref->m_ext_storage, so the additional indirection is 
already performed.

References:
- MCLADDREFERENCE() incrementing the wrong ext_refcnt?
  - From: Edgar Fuß
- Re: MCLADDREFERENCE() incrementing the wrong ext_refcnt?
  - From: Ryota Ozaki

Prev by Date: [GSoC] Questions about emulating missing linux system calls project
Next by Date: Inquiry about the "Auto Create Swap on Memory Pressure" Project in GSoC
Previous by Thread: Re: MCLADDREFERENCE() incrementing the wrong ext_refcnt?
Next by Thread: Forcing a USB device to "ugen"
Indexes:

Home | Main Index | Thread Index | Old Index