All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Akihiko Odaki" <akihiko.odaki@daynix.com>,
	qemu-devel@nongnu.org,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH] util/vfio-helpers: Use g_file_read_link()
Date: Mon, 22 May 2023 13:44:29 +0100	[thread overview]
Message-ID: <ZGtjrWPItBSV6wQi@redhat.com> (raw)
In-Reply-To: <ccdf88d1-54de-453f-b600-1f0f562aae31@linaro.org>

On Mon, May 22, 2023 at 02:38:44PM +0200, Philippe Mathieu-Daudé wrote:
> On 22/5/23 13:49, Akihiko Odaki wrote:
> > When _FORTIFY_SOURCE=2, glibc version is 2.35, and GCC version is
> > 12.1.0, the compiler complains as follows:
> > 
> > In file included from /usr/include/features.h:490,
> >                   from /usr/include/bits/libc-header-start.h:33,
> >                   from /usr/include/stdint.h:26,
> >                   from /usr/lib/gcc/aarch64-unknown-linux-gnu/12.1.0/include/stdint.h:9,
> >                   from /home/alarm/q/var/qemu/include/qemu/osdep.h:94,
> >                   from ../util/vfio-helpers.c:13:
> > In function 'readlink',
> >      inlined from 'sysfs_find_group_file' at ../util/vfio-helpers.c:116:9,
> >      inlined from 'qemu_vfio_init_pci' at ../util/vfio-helpers.c:326:18,
> >      inlined from 'qemu_vfio_open_pci' at ../util/vfio-helpers.c:517:9:
> > /usr/include/bits/unistd.h:119:10: error: argument 2 is null but the corresponding size argument 3 value is 4095 [-Werror=nonnull]
> >    119 |   return __glibc_fortify (readlink, __len, sizeof (char),
> >        |          ^~~~~~~~~~~~~~~
> > 
> > This error implies the allocated buffer can be NULL. Use
> > g_file_read_link(), which allocates buffer automatically to avoid the
> > error.
> > 
> > Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> > ---
> >   util/vfio-helpers.c | 8 +++++---
> >   1 file changed, 5 insertions(+), 3 deletions(-)
> > 
> > diff --git a/util/vfio-helpers.c b/util/vfio-helpers.c
> > index 2d8af38f88..e482ab22e2 100644
> > --- a/util/vfio-helpers.c
> > +++ b/util/vfio-helpers.c
> > @@ -106,15 +106,17 @@ struct QEMUVFIOState {
> >    */
> >   static char *sysfs_find_group_file(const char *device, Error **errp)
> >   {
> > +    g_autoptr(GError) gerr;
> 
> Shouldn't this also be NULL-initialized (other picky compilers)?

Yes, *all* use of g_auto* must have an initializer at time of
declaration.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2023-05-22 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 11:49 [PATCH] util/vfio-helpers: Use g_file_read_link() Akihiko Odaki
2023-05-22 12:38 ` Philippe Mathieu-Daudé
2023-05-22 12:44   ` Daniel P. Berrangé [this message]
2023-05-22 12:47 ` Cédric Le Goater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZGtjrWPItBSV6wQi@redhat.com \
    --to=berrange@redhat.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=alex.williamson@redhat.com \
    --cc=clg@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.