All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: Yodel Eldar <yodel.eldar@yodel.dev>, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/9] tests/test_vhost_user_bridge: skip when running ASAN
Date: Mon, 7 Sep 2026 15:32:16 -0400	[thread overview]
Message-ID: <20260907152927-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJ+F1CKiUFGqJbWuxNM54bPJg1AicBKK_i+AuXttSCy-JRr8xg@mail.gmail.com>

On Mon, Sep 07, 2026 at 06:18:39PM +0400, Marc-André Lureau wrote:
> Hi
> 
> On Mon, Sep 7, 2026 at 5:35 PM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Mon, Sep 07, 2026 at 05:22:43PM +0400, Marc-André Lureau wrote:
> > > > maybe just avoid stdbuf completely.
> > > > i don't remember why we use it, but it looks like merely to
> > > > disable buffering for stdout?
> > > >
> > > > If so:
> > > >
> > > > setvbuf(stdout, NULL, _IONBF, 0);
> > > >
> > > > will do just that with no asan issues.
> > > >
> > >
> > > That requires modifying vhost-user-bridge, not sure that's what we want.
> > >
> > > thanks
> >
> > why not? it's not like it's a facility useful outside of testing qemu.
> > If we were we'd probably disable stdout printout completely.
> 
> Since the test redirects stderr to stdout, I guess the log is
> fully-buffered for stdout and unbuffered for stderr, and we see stderr
> log lines in the file log before the others. If we call
> setvbuf(stdout, NULL, _IONBF, 0) early, we probably will get
> interleaved stream output, but probably broken lines...

We can also just change that macro to write to stderr.

> Tbh, I don't
> have much motivation to check or fix this, I would just like the test
> to be green or skipped when built with ASAN. The current workaround is
> quite ok. If you prefer setvbuf() in vhost-user-bridge.c, I am okay
> too.
> 
> Yodel, wdyt?



  reply	other threads:[~2026-09-07 19:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-06  8:53 [PATCH 0/9] Various ASAN & tests fixes Marc-André Lureau
2026-09-06  8:53 ` [PATCH 1/9] tests: fix qemu:func-hexagon-linters Marc-André Lureau
2026-09-06 22:30   ` Brian Cain
2026-09-06  8:53 ` [PATCH 2/9] tests/test_vhost_user_bridge: skip when running ASAN Marc-André Lureau
2026-09-07 12:02   ` Michael S. Tsirkin
2026-09-07 13:22     ` Marc-André Lureau
2026-09-07 13:34       ` Michael S. Tsirkin
2026-09-07 14:18         ` Marc-André Lureau
2026-09-07 19:32           ` Michael S. Tsirkin [this message]
2026-09-06  8:53 ` [PATCH 3/9] hw/misc/bcm2835_powermgt: free wdog timer on finalize Marc-André Lureau
2026-09-06  8:53 ` [PATCH 4/9] tests/launchupdate-test: correct g_auto usage Marc-André Lureau
2026-09-06  8:53 ` [PATCH 5/9] tests/launchupdate-test: correctly release qs Marc-André Lureau
2026-09-06  8:53 ` [PATCH 6/9] tests/launchupdate-test: fix fw_cfg leak Marc-André Lureau
2026-09-06  8:53 ` [PATCH 7/9] igvm: release found memory region on success Marc-André Lureau
2026-09-06  8:53 ` [PATCH 8/9] igvm: make IgvmMemoryRegion a QOM Marc-André Lureau
2026-09-06  8:53 ` [PATCH 9/9] hw/s390x/ipl: fix short SCSI loadparm buffer over-read Marc-André Lureau
2026-09-08 13:55   ` Jared Rossi
2026-09-09  0:03   ` Eric Farman

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=20260907152927-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yodel.eldar@yodel.dev \
    /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.