public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Yalan Zhang <yalzhang@redhat.com>
Subject: Re: [PATCH v2 4/6] log: Add _perror() logging function variants
Date: Wed, 19 Jun 2024 10:38:08 +0200	[thread overview]
Message-ID: <20240619103801.3a6088cd@elisabeth> (raw)
In-Reply-To: <ZnJAxJ-ffL8r5P1G@zatzit>

On Wed, 19 Jun 2024 12:21:56 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> On Tue, Jun 18, 2024 at 09:14:25AM +0200, Stefano Brivio wrote:
> > In many places, we have direct perror() calls, which completely bypass
> > logging functions and log files.
> > 
> > They are definitely convenient: offer similar convenience with
> > _perror() logging variants, so that we can drop those direct perror()
> > calls.
> > 
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> > ---
> >  log.c | 21 +++++++++++++++++++++
> >  log.h | 21 +++++++++++++++++----
> >  2 files changed, 38 insertions(+), 4 deletions(-)
> > 
> > diff --git a/log.c b/log.c
> > index 5853496..9ddc58c 100644
> > --- a/log.c
> > +++ b/log.c
> > @@ -79,6 +79,11 @@ void vlogmsg(int pri, const char *format, va_list ap)
> >  	}
> >  }
> >  
> > +/**
> > + * logmsg() - vlogmsg() wrapper for variable argument lists
> > + * @pri:	Facility and level map, same as priority for vsyslog()
> > + * @format:	Message
> > + */
> >  void logmsg(int pri, const char *format, ...)
> >  {
> >  	va_list ap;
> > @@ -88,6 +93,22 @@ void logmsg(int pri, const char *format, ...)
> >  	va_end(ap);
> >  }
> >  
> > +/**
> > + * logmsg_perror() - vlogmsg() wrapper with perror()-like functionality
> > + * @pri:	Facility and level map, same as priority for vsyslog()
> > + * @format:	Message
> > + */
> > +void logmsg_perror(int pri, const char *format, ...)
> > +{
> > +	va_list ap;
> > +
> > +	va_start(ap, format);
> > +	vlogmsg(pri, format, ap);
> > +	va_end(ap);
> > +
> > +	logmsg(pri, ": %s", strerror(errno));  
> 
> The vlogmsg() above could invoke syscalls which clobber errno, so you
> need to save it beforehand.

Oops, nice catch.

-- 
Stefano


  reply	other threads:[~2024-06-19  8:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18  7:14 [PATCH v2 0/6] Fixes for early logging/prints and related cleanups Stefano Brivio
2024-06-18  7:14 ` [PATCH v2 1/6] conf, passt: Don't try to log to stderr after we close it Stefano Brivio
2024-06-19  2:14   ` David Gibson
2024-06-19  8:34     ` Stefano Brivio
2024-06-20  0:16       ` David Gibson
2024-06-18  7:14 ` [PATCH v2 2/6] conf, log: Instead of abusing log levels, add log_conf_parsed flag Stefano Brivio
2024-06-18  7:14 ` [PATCH v2 3/6] log, passt: Always print to stderr before initialisation is complete Stefano Brivio
2024-06-18  7:14 ` [PATCH v2 4/6] log: Add _perror() logging function variants Stefano Brivio
2024-06-19  2:21   ` David Gibson
2024-06-19  8:38     ` Stefano Brivio [this message]
2024-06-18  7:14 ` [PATCH v2 5/6] treewide: Replace perror() calls with calls to logging functions Stefano Brivio
2024-06-19  2:24   ` David Gibson
2024-06-18  7:14 ` [PATCH v2 6/6] treewide: Replace strerror() calls Stefano Brivio
2024-06-19  2:29   ` David Gibson
2024-06-19  8:36     ` Stefano Brivio

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=20240619103801.3a6088cd@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=yalzhang@redhat.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).