Hi, Besides fstat(), I have also found when call malloc() and fopen(), there are serveral places that do not check their return value.
Though it is a small probability for the two functions to fail, but it is better to fix them. So i added these patches to this patch-set v2 -> v3: -ivshmem: change the error message which advised by Levente Kurusa -others: add six new patches which check the return value of malloc() and fopen(), - which may be failed. v1 -> v2: -ivshmem: modified the log message according to reviewing suggestion of Michael Li Liu (3): tcg: check return value of fopen() block/vvfat: fix setbuf stream parameter may be NULL qtest: check the value returned by fopen() zhanghailiang (7): l2cap: fix access freed memory monitor: fix access freed memory virtio-blk: fix reference a pointer which might be freed ivshmem: check the value returned by fstat() util/path: check return value of malloc() slirp: check return value of malloc() linux-user: check return value of malloc() block/vvfat.c | 5 ++++- hw/block/virtio-blk.c | 5 +++-- hw/bt/l2cap.c | 2 +- hw/misc/ivshmem.c | 6 +++++- linux-user/syscall.c | 3 +++ monitor.c | 4 +++- qtest.c | 5 +++++ slirp/misc.c | 8 ++++++-- tcg/tcg.c | 4 ++++ tests/bios-tables-test.c | 2 ++ util/path.c | 9 ++++++--- 11 files changed, 42 insertions(+), 11 deletions(-) -- 1.7.12.4