From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Vitaly Chikunov <vt@altlinux.org>,
"Dmitry V . Levin" <ldv@altlinux.org>, Greg Kurz <groug@kaod.org>
Subject: Re: [PULL 0/5] 9p queue 2022-02-10
Date: Mon, 14 Feb 2022 13:09:48 +0100 [thread overview]
Message-ID: <2563382.p5drSlMS5x@silver> (raw)
In-Reply-To: <CAFEAcA9vHYw=hKaRqw4LBk7dHReR43duoCCEpH-VC2sEXoQKHA@mail.gmail.com>
On Montag, 14. Februar 2022 10:55:17 CET Peter Maydell wrote:
> On Mon, 14 Feb 2022 at 09:47, Christian Schoenebeck
>
> <qemu_oss@crudebyte.com> wrote:
> > So this is about the 'dirent' patch:
> > https://github.com/cschoenebeck/qemu/commit/de19c79dad6a2cad54ae04ce754d47
> > c07bf9bc93
> >
> > In conjunction with the 9p fuzzing tests:
> > https://wiki.qemu.org/Documentation/9p#Fuzzing
> >
> > I first thought it might be a false positive due to the unorthodox
> > handling of dirent duplication by that patch, but from the ASan output
> > below I am not really sure about that.
> >
> > Is there a way to get the content of local variables?
>
> Yes. You can build locally with the clang sanitizers enabled and then
> run under gdb and with the appropriate environment variables to tell the
> sanitizer to abort() on failures.
Well, it does no longer matter for this particular issue here, but it would be
useful if the CI scripts would already dump the local variables to the logs.
E.g. because the patch in question was about system dependant variations.
Another reason is the random data nature of fuzzing tests. Even though the
latter could probably be reproduced with an appropriate seed.
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2022-02-14 12:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 11:21 [PULL 0/5] 9p queue 2022-02-10 Christian Schoenebeck
2022-02-10 11:21 ` [PULL 1/5] tests/9pfs: use g_autofree where possible Christian Schoenebeck
2022-02-10 11:21 ` [PULL 4/5] tests/9pfs: Use g_autofree and g_autoptr " Christian Schoenebeck
2022-02-10 11:21 ` [PULL 3/5] tests/9pfs: Fix leak of local_test_path Christian Schoenebeck
2022-02-10 11:21 ` [PULL 2/5] tests/9pfs: fix mkdir() being called twice Christian Schoenebeck
2022-02-10 11:21 ` [PULL 5/5] 9pfs: Fix segfault in do_readdir_many caused by struct dirent overread Christian Schoenebeck
2022-02-13 20:33 ` [PULL 0/5] 9p queue 2022-02-10 Peter Maydell
2022-02-14 9:47 ` Christian Schoenebeck
2022-02-14 9:55 ` Peter Maydell
2022-02-14 12:09 ` Christian Schoenebeck [this message]
2022-02-14 10:36 ` Greg Kurz
2022-02-14 11:44 ` Christian Schoenebeck
2022-02-14 14:43 ` Vitaly Chikunov
2022-02-14 17:40 ` Christian Schoenebeck
2022-02-15 7:01 ` Greg Kurz
2022-02-16 10:30 ` Christian Schoenebeck
2022-02-16 14:23 ` Greg Kurz
2022-02-16 15:19 ` Philippe Mathieu-Daudé via
2022-02-16 16:09 ` Vitaly Chikunov
2022-02-16 16:20 ` Christian Schoenebeck
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=2563382.p5drSlMS5x@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=ldv@altlinux.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vt@altlinux.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 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 NNTP newsgroup(s).