Experimental Physics and
Industrial Control System

2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024	Index	2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024
<== Date ==>		<== Thread ==>

Subject:	AW: Long PV names in EPICS base
From:	"Zimoch Dirk \(PSI\) via Core-talk" <core-talk at aps.anl.gov>
To:	"Zimoch Dirk (PSI)" <dirk.zimoch at psi.ch>, Simon Rose <Simon.Rose at ess.eu>
Cc:	"core-talk at aps.anl.gov" <core-talk at aps.anl.gov>
Date:	Fri, 14 Jan 2022 09:55:05 +0000

I mean : If not recompiled. E.g., not your program but some user's who brought the compiled program with them.

Programs assuming that PVNAME_STRINGSZ is always enough memory to store a record name unchecked may get buffer overruns.

Von: Core-talk <core-talk-bounces at aps.anl.gov> Im Auftrag von Simon Rose via Core-talk
Gesendet: Freitag, 14. Januar 2022 09:32
An: AppVeyor via Core-talk <core-talk at aps.anl.gov>
Betreff: Long PV names in EPICS base

Hi all -

Suppose that we wanted to allow EPICS to have longer PV names than the default 60 characters. It seems that this is possible by modifying two files:

PVNAME_STRINGSZ in modules/libcom/src/misc/dbDefs.h
The “Record Name” field in modules/database/src/ioc/db/dbCommon.dbd.pod

If you modify these two locations, then you can have records with PVs whose names are longer. ca/pvget/put seem to work find regardless, so this seems like a very simple change. However…

Is there anything else that is missing that would need to be changed here? In particular, I wonder if there are any concerns with linking records to each other, or any other unexpected consequences.

Thanks,

______________________