Re: [dpdk-dev] [PATCH] pmdinfogen: allow padding after NUL terminator

2021-05-27 Thread David Marchand
On Wed, May 26, 2021 at 11:44 PM Dmitry Kozlyuk wrote: > > Size of string constant symbol may be larger than its length > measured up to NUL terminator. In this case pmdinfogen included padding > bytes after NUL terminator in generated source, yielding incorrect code. > > Always trim string data t

Re: [dpdk-dev] [PATCH] pmdinfogen: allow padding after NUL terminator

2021-05-27 Thread Dmitry Kozlyuk
On Thu, May 27, 2021, 09:53 David Marchand wrote: > Just to confirm my reading of the C version of pmdinfogen: the C version > formats those symbols fine with printf %s. > So there should be no need for a fix in stable branches, right? > Yes. >

Re: [dpdk-dev] [PATCH] pmdinfogen: allow padding after NUL terminator

2021-05-26 Thread David Marchand
On Wed, May 26, 2021 at 11:44 PM Dmitry Kozlyuk wrote: > > Size of string constant symbol may be larger than its length > measured up to NUL terminator. In this case pmdinfogen included padding > bytes after NUL terminator in generated source, yielding incorrect code. > > Always trim string data t

[dpdk-dev] [PATCH] pmdinfogen: allow padding after NUL terminator

2021-05-26 Thread Dmitry Kozlyuk
Size of string constant symbol may be larger than its length measured up to NUL terminator. In this case pmdinfogen included padding bytes after NUL terminator in generated source, yielding incorrect code. Always trim string data to NUL terminator while reading ELF. It was already done for COFF be