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 wit
Chen Gang 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 Gang
> ---
> hw/
On 03/03/2014 04:34 PM, Markus Armbruster wrote:
> Chen Gang 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 re
Chen Gang 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 qemu-devel):
>
>-
"Aneesh Kumar K.V" writes:
> Chen Gang 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 will also have to go through
> the rest
On 03/04/2014 03:29 AM, Aneesh Kumar K.V wrote:
> "Aneesh Kumar K.V" writes:
>
>> Chen Gang writes:
>> Can we keep this as
>> v9fs_co_run_in_worker(
>> {
>>
>>buf->data = __readlink(&s->ctx, path);
>>
>> }
>>
>> I can do that change f
