From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Dan Schatzberg <dschatzberg@fb.com>, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH] 9pfs: Fix divide by zero bug
Date: Fri, 22 Nov 2019 22:53:09 +0100 [thread overview]
Message-ID: <1786866.o8IioZIX2y@silver> (raw)
In-Reply-To: <20191122200034.122564-1-dschatzberg@fb.com>
On Freitag, 22. November 2019 21:00:34 CET Dan Schatzberg wrote:
> Some filesystems may return 0s in statfs (trivially, a FUSE filesystem
> can do so). QEMU should handle this gracefully and just behave the
> same as if statfs failed.
Is that actually legal in non-error cases? Shouldn't a driver without a block
size concept return 512 according to POSIX?
> Signed-off-by: Dan Schatzberg <dschatzberg@fb.com>
> ---
> hw/9pfs/9p.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/hw/9pfs/9p.c b/hw/9pfs/9p.c
> index 37abcdb71e..520177f40c 100644
> --- a/hw/9pfs/9p.c
> +++ b/hw/9pfs/9p.c
> @@ -1834,8 +1834,10 @@ static int32_t coroutine_fn get_iounit(V9fsPDU *pdu,
> V9fsPath *path) * and as well as less than (client msize - P9_IOHDRSZ))
> */
> if (!v9fs_co_statfs(pdu, path, &stbuf)) {
> - iounit = stbuf.f_bsize;
> - iounit *= (s->msize - P9_IOHDRSZ)/stbuf.f_bsize;
> + if (stbuf.f_bsize) {
> + iounit = stbuf.f_bsize;
> + iounit *= (s->msize - P9_IOHDRSZ) / stbuf.f_bsize;
> + }
> }
> if (!iounit) {
> iounit = s->msize - P9_IOHDRSZ;
Nevertheless, since that will leave iounit initialized with zero and since
there is already an !ionunit case handling there ...
Acked-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2019-11-22 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 20:00 [PATCH] 9pfs: Fix divide by zero bug Dan Schatzberg
2019-11-22 21:53 ` Christian Schoenebeck [this message]
2019-11-23 15:29 ` 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=1786866.o8IioZIX2y@silver \
--to=qemu_oss@crudebyte.com \
--cc=dschatzberg@fb.com \
--cc=groug@kaod.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).