| commit | ff55e94d23ae94c8628b0115320157c763eb3e06 | |
| author | Li Qiang <liqiang6-s@360.cn> | |
| Mon, 17 Oct 2016 12:13:58 +0000 (17 14:13 +0200) | ||
| committer | Greg Kurz <groug@kaod.org> | |
| Mon, 17 Oct 2016 12:13:58 +0000 (17 14:13 +0200) | ||
| tree | 4c0e0e19c59eaf75b260996d2481c96f146deaac | treesnapshot (tar.gz zip) |
| parent | eb687602853b4ae656e9236ee4222609f3a6887d | commitdiff |
9pfs: fix memory leak in v9fs_xattrcreate
The 'fs.xattr.value' field in V9fsFidState object doesn't consider the
situation that this field has been allocated previously. Every time, it
will be allocated directly. This leads to a host memory leak issue if
the client sends another Txattrcreate message with the same fid number
before the fid from the previous time got clunked.
Signed-off-by: Li Qiang <liqiang6-s@360.cn>
Reviewed-by: Greg Kurz <groug@kaod.org>
[groug, updated the changelog to indicate how the leak can occur]
Signed-off-by: Greg Kurz <groug@kaod.org>
The 'fs.xattr.value' field in V9fsFidState object doesn't consider the
situation that this field has been allocated previously. Every time, it
will be allocated directly. This leads to a host memory leak issue if
the client sends another Txattrcreate message with the same fid number
before the fid from the previous time got clunked.
Signed-off-by: Li Qiang <liqiang6-s@360.cn>
Reviewed-by: Greg Kurz <groug@kaod.org>
[groug, updated the changelog to indicate how the leak can occur]
Signed-off-by: Greg Kurz <groug@kaod.org>
| hw/9pfs/9p.c | diffblobblamehistory |