Chen Gang gang.chen.5...@gmail.com writes:
When path is truncated by PATH_MAX limitation, it causes QEMU to access
incorrect file. So use original full path instead of PATH_MAX within
9pfs (need check/process ENOMEM for related memory allocation).
The related test:
[...]
Signed-off-by: Chen
On 03/03/2014 04:34 PM, Markus Armbruster wrote:
Chen Gang gang.chen.5...@gmail.com writes:
When path is truncated by PATH_MAX limitation, it causes QEMU to access
incorrect file. So use original full path instead of PATH_MAX within
9pfs (need check/process ENOMEM for related memory
Chen Gang gang.chen.5...@gmail.com writes:
When path is truncated by PATH_MAX limitation, it causes QEMU to access
incorrect file. So use original full path instead of PATH_MAX within
9pfs (need check/process ENOMEM for related memory allocation).
The related test:
- Environments (for
Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com writes:
Chen Gang gang.chen.5...@gmail.com writes:
Can we keep this as
v9fs_co_run_in_worker(
{
buf-data = __readlink(s-ctx, path);
}
I can do that change for you if you want. I
On 03/04/2014 03:29 AM, Aneesh Kumar K.V wrote:
Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com writes:
Chen Gang gang.chen.5...@gmail.com writes:
Can we keep this as
v9fs_co_run_in_worker(
{
buf-data = __readlink(s-ctx, path);
When path is truncated by PATH_MAX limitation, it causes QEMU to access
incorrect file. So use original full path instead of PATH_MAX within
9pfs (need check/process ENOMEM for related memory allocation).
The related test:
- Environments (for qemu-devel):
- Host is under fedora17 desktop
