From: Jevon Qiao <qiaojianfeng@unitedstack.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: haomaiwang@gmail.com, mst@redhat.com, qemu-devel@nongnu.org,
aneesh.kumar@linux.vnet.ibm.com, sage@newdream.net,
ceph-devel@vger.kernel.org, gfarnum@redhat.com
Subject: Re: [Qemu-devel] [PATCH] hw/9pfs: Add CephFS support in VirtFS
Date: Mon, 14 Mar 2016 10:02:43 +0800 [thread overview]
Message-ID: <56E61BC3.1010505@unitedstack.com> (raw)
In-Reply-To: <20160309200243.5b00eea7@bahia.lab.toulouse-stg.fr.ibm.com>
Hi Greg,
Thank you very much for reviewing the code, I've revised the code per
your comments, will post it later. Meanwhile, please see my answers to
your questions below.
>
>> + }
>> + fs->dir = (DIR *)result;
>> + if (!fs->dir) {
>> + fprintf(stderr, "ceph_opendir return NULL for ceph_dir_result\n");
> Hmm... is this a message for the QEMU user, so that she can fix something and
> retry ? I suspect it is more for debugging purposes, in which case I'd rather
> add a result argument to trace_cephfs_opendir_return() above.
Actually, this message is mainly used for debugging.
> And BTW, can ceph_opendir() return success without filling the structure ?
I double checked the Ceph code, it can not. I've removed this error message.
>> +
>> +# hw/9pfs/9p-cephfs.c
>> +cephfs_lstat_return(char *path, int stmode, int stuid, int stgid, int stsize, int ret) "path %s stmode %d stuid %d stgid %d stsize %d ret %d"
>> +cephfs_readlink_return(char *path, int ret) "path %s ret %d"
>> +cephfs_open_return(char *path, int flags, int mode, int fd) "path %s flags %d mode %d fd %d"
>> +cephfs_opendir_return(char *path, int ret) "path %s ret %d"
>> +cephfs_rewinddir(void *dir) "dir %p"
>> +cephfs_telldir(void *dir) "dir %p"
>> +cephfs_readdir_r_return(void *tmpent, void *entry, int ret) "tmpent %p entry %p ret %d"
>> +cephfs_seekdir(void *dir, int off) "dir %p off %d"
>> +cephfs_preadv(int iovcnt, int len) "iovcnt %d len %d"
>> +cephfs_preadv_return(int iovcnt, int len, long ret) "iovcnt %d len %d ret %l"
> ret %ld
>
>> +cephfs_pwritev(int iovcnt, int len, int offset) "iovcnt %d len %d offset %d"
>> +cephfs_pwritev_return(int iovcnt, int len, int offset, long ret) "iovcnt %d len %d offset %d ret %l"cephfs_chmod(char *path, int fcmode) "path %s fcmode %d"
> ret %ld for cephfs_pwritev_return() and missing newline before cephfs_chmod()
>
> I'm wondering if this patch was build tested before being posted to the list.
Good catch. Yes, the code had been compiled and tested. However, it
seems the compiler will not report this error until the trace point is
used. Since 'cephfs_chmod' is not used in 9p-cephfs.c, so I just forget
to test it. That's why the error was not found. I've already removed
this trace point in the revision.
Thanks,
Jevon
>> +cephfs_chmod_return(char *path, int fcmode, int ret) "path %s fcmode %d ret %d"
>> +cephfs_mknod_return(char *path, int fcmode, uint32_t fcrdev, int ret) "path %s fcmode %d fcrdev %u ret %d"
>> +cephfs_mkdir_return(char *path, int fcmode, int ret) " path %s fcmode %d ret %d"
>> +cephfs_fstat_return(int fidtype, int fd, int stuid, int stgid, int stsize, int ret) "fidtype %d fd %d stuid %d stgid %d stsize %d ret %d"
>> +cephfs_open2_return(char *path, int flags, int fcmode) "path %s flags %d fcmode %d"
next prev parent reply other threads:[~2016-03-14 2:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 15:41 [Qemu-devel] [PATCH] hw/9pfs: Add CephFS support in VirtFS Jevon Qiao
2016-03-08 0:51 ` Jevon Qiao
2016-03-09 9:59 ` Greg Kurz
2016-03-09 19:02 ` Greg Kurz
2016-03-09 20:09 ` Eric Blake
2016-03-10 9:08 ` Greg Kurz
2016-03-14 2:02 ` Jevon Qiao [this message]
[not found] <1457971368-1335-1-git-send-email-scaleqiao@gmail.com>
2016-03-15 9:30 ` Greg Kurz
2016-03-15 13:39 ` Jevon Qiao
2016-03-15 13:46 ` Greg Kurz
2016-03-15 14:16 ` Jevon Qiao
2016-04-05 15:27 ` Jevon Qiao
2016-04-05 15:31 ` Greg Kurz
2016-04-06 4:28 ` Jevon Qiao
2016-03-15 13:52 ` Michael S. Tsirkin
2016-03-15 14:33 ` Jevon Qiao
2016-04-07 15:50 ` Greg Kurz
2016-04-10 6:55 ` Jevon Qiao
2016-04-13 14:20 ` Greg Kurz
2016-04-16 18:53 ` Aneesh Kumar K.V
2016-04-15 12:01 ` Greg Kurz
2016-04-15 13:21 ` 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=56E61BC3.1010505@unitedstack.com \
--to=qiaojianfeng@unitedstack.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=haomaiwang@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sage@newdream.net \
/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).