From: Greg Kurz <groug@kaod.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PULL 0/8] 9p patches for 2.8 20160916
Date: Fri, 16 Sep 2016 16:39:55 +0200 [thread overview]
Message-ID: <20160916163955.3460f28b@bahia> (raw)
In-Reply-To: <CAFEAcA8z4vYDWBGxQCUpncwRuDHbmLE22zNgWEcB5gWVW=3P_g@mail.gmail.com>
On Fri, 16 Sep 2016 15:25:42 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 16 September 2016 at 14:09, Greg Kurz <groug@kaod.org> wrote:
> > The following changes since commit 5f473241ac595452ae0638dc63e7af2a2294f5ec:
> >
> > Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2016-09-15 18:12:40 +0100)
> >
> > are available in the git repository at:
> >
> > https://github.com/gkurz/qemu.git tags/for-upstream
> >
> > for you to fetch changes up to 5c574f1bf92cfaf4aae6cbb66b79066c654920e1:
> >
> > 9pfs: fix potential segfault during walk (2016-09-16 12:16:29 +0200)
> >
> > ----------------------------------------------------------------
> > This pull request contains:
> > - a fix for a regression introduced in 2.7
> > - basic functional testing for virtio-9p
> > - some code cleanups for 9pfs
> >
> > ----------------------------------------------------------------
>
> Fails test on ppc64be:
>
> /i386/virtio/9p/pci/basic/transaction: **
> ERROR:/home/pm215/qemu/tests/virtio-9p-test.c:167:pci_basic_transaction:
> assertion failed (hdr.size
> < (uint32_t) P9_MAX_SIZE): (603979776 < 8192)
> FAIL
> GTester: last random seed: R02S0ce79f32586824bc8cbd5461f009c62a
> (pid=33294)
>
> Looks like an endianness bug.
>
Ok, I'll look into it... but the important part in this pull request is
the "9pfs: fix potential segfault during walk" patch. It fixes a regression
introduced in 2.7 by the 9P security fixes. And IIUC, Michael Roth is about
to release 2.6.1.1 with these fixes and the regression...
Should I send a new pull request without the qtest patches ? Or with the
regression fix only ?
Please advise.
Thanks.
--
Greg
> thanks
> -- PMM
next prev parent reply other threads:[~2016-09-16 14:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:09 [Qemu-devel] [PULL 0/8] 9p patches for 2.8 20160916 Greg Kurz
2016-09-16 13:09 ` [Qemu-devel] [PULL 1/8] 9pfs: drop unused fmt strings in the proxy backend Greg Kurz
2016-09-16 13:09 ` [Qemu-devel] [PULL 2/8] 9pfs: drop duplicate line in " Greg Kurz
2016-09-16 13:09 ` [Qemu-devel] [PULL 3/8] 9pfs: drop useless v9fs_string_null() function Greg Kurz
2016-09-16 13:09 ` [Qemu-devel] [PULL 4/8] 9pfs: introduce v9fs_path_sprintf() helper Greg Kurz
2016-09-16 13:09 ` [Qemu-devel] [PULL 5/8] tests: virtio-9p: introduce start/stop functions Greg Kurz
2016-09-16 13:09 ` [Qemu-devel] [PULL 6/8] tests: virtio-9p: add basic configuration test Greg Kurz
2016-09-16 13:09 ` [Qemu-devel] [PULL 7/8] tests: virtio-9p: add basic transaction test Greg Kurz
2016-09-16 13:09 ` [Qemu-devel] [PULL 8/8] 9pfs: fix potential segfault during walk Greg Kurz
2016-09-16 14:25 ` [Qemu-devel] [PULL 0/8] 9p patches for 2.8 20160916 Peter Maydell
2016-09-16 14:39 ` Greg Kurz [this message]
2016-09-16 14:46 ` Peter Maydell
2016-09-16 17:36 ` Greg Kurz
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=20160916163955.3460f28b@bahia \
--to=groug@kaod.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=peter.maydell@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 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).