| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: How to safely implement an asynPortDriver with SCAN records |
| From: | Jure Varlec via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Michael Davidsaver <mdavidsaver at gmail.com>, Érico Nogueira Rolim <erico.rolim at lnls.br> |
| Cc: | tech-talk <tech-talk at aps.anl.gov> |
| Date: | Wed, 20 Jul 2022 18:51:25 +0000 |
|
> imo. it is reasonable to join worker threads here, but I would
> recommend against deleting.
> > Please keep in mind that delete
leaves dangling pointers in the
> asyn port. imo. this is an
invitation for the chaos of
> use-after-free errors. Could be, but I can't see how. The IOC is shutting down, asynManager is rejecting queueRequest calls to a disabled port (which is what the device support code uses), and asyn doesn't register any hooks that I can see. So AFAICT, when the records are the only users of the port, there should be no chaos. Are you just trying to be careful, or are you aware of something I missed? If I'm wrong about this, I'd love to know before I have to face the chaos :) . Best,
Jure
|