| commit | 926487b70be7cfd0303168a68a092bc6faf122ca | |
| author | Sripathi Kodi <sripathik@in.ibm.com> | |
| Wed, 9 Jun 2010 09:03:22 +0000 (9 14:33 +0530) | ||
| committer | Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> | |
| Wed, 8 Sep 2010 17:26:39 +0000 (8 22:56 +0530) | ||
| tree | 35949e47058804214fac912e6ede267a3ef1ddf8 | treesnapshot (tar.gz zip) |
| parent | be940c8716d4d7783b1649f5f286b4c0187f9f6d | commitdiff |
virtio-9p: Return correct error from v9fs_remove
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
In v9fs_remove_post_remove() we currently ignore the error returned by
the previous call to remove() and return an error only if freeing the
fid fails. However, the client expects to see the error from remove().
Currently the client falsely thinks that the remove call has always
succeeded. For example, doing rmdir on a non-empty directory does
not return ENOTEMPTY.
With this patch we ignore the error from free_fid(). The client cannot
use this error value anyway.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
In v9fs_remove_post_remove() we currently ignore the error returned by
the previous call to remove() and return an error only if freeing the
fid fails. However, the client expects to see the error from remove().
Currently the client falsely thinks that the remove call has always
succeeded. For example, doing rmdir on a non-empty directory does
not return ENOTEMPTY.
With this patch we ignore the error from free_fid(). The client cannot
use this error value anyway.
Signed-off-by: Sripathi Kodi <sripathik@in.ibm.com>
Signed-off-by: Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>
| hw/virtio-9p.c | diffblobblamehistory |