EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: unsymmetrical mutex use in dbCa.c
From: "Jeff Hill" <[email protected]>
To: "'Dirk Zimoch'" <[email protected]>, <[email protected]>
Date: Wed, 8 Jun 2011 08:41:50 -0600
> By coincidence I found a strange thing in src/db/dbCa.c. Some functions
> call epicsMutexUnlock(pca->lock) without taking the lock first.

I created a bug entry

https://bugs.launchpad.net/epics-base/+bug/794595

Jeff
______________________________________________________
Jeffrey O. Hill           Email        [email protected]
LANL MS H820              Voice        505 665 1831
Los Alamos NM 87545 USA   FAX          505 665 5107

Message content: TSPA

With sufficient thrust, pigs fly just fine. However, this is
not necessarily a good idea. It is hard to be sure where they
are going to land, and it could be dangerous sitting under them
as they fly overhead. -- RFC 1925


> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Dirk Zimoch
> Sent: Wednesday, June 08, 2011 7:54 AM
> To: [email protected]
> Subject: unsymmetrical mutex use in dbCa.c
> 
> Hi all (gurus especially)
> 
> By coincidence I found a strange thing in src/db/dbCa.c. Some functions
> call epicsMutexUnlock(pca->lock) without taking the lock first.
> 
> Example:
> 
> long epicsShareAPI dbCaGetNelements(
>      const struct link *plink,long *nelements)
> {
>      caLink    *pca;
> 
>      pcaGetCheck
>      *nelements = pca->nelements;
>      epicsMutexUnlock(pca->lock);
>      return(0);
> }
> 
> This looks quite wrong to me. Am I missing something or is this a bug?
> 
> These are the functions
> * dbCaGetNelements
> * dbCaGetSevr
> * dbCaGetTimeStamp
> * dbCaGetLinkDBFtype
> * dbCaGetControlLimits
> * dbCaGetGraphicLimits
> * dbCaGetAlarmLimits
> * dbCaGetPrecision
> * dbCaGetUnits
> 
> 
> Dirk




References:
unsymmetrical mutex use in dbCa.c Dirk Zimoch

Navigate by Date:
Prev: Re: unsymmetrical mutex use in dbCa.c Dirk Zimoch
Next: RE: general purpose callback tasks : callbackRequest() Davidsaver, Michael
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: unsymmetrical mutex use in dbCa.c Dirk Zimoch
Next: Request for opinions about device driver/support Gurd Pamela EXT
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·